HubSpot agent tool names the action, not your company
Name the tool like a plain job to be done, starting with a verb, instead of cramming your brand into the title.
Why this can grow a startup
Agent tools get harder to trust when the naming sounds like marketing copy or internal jargon. HubSpot's naming rules push in the opposite direction. Tool names should start with a verb, stay between three and seven words, and skip organization attributions because the UI already handles association. Descriptions should be short, concrete, and written in present tense. The result is a tool shelf that reads like real work someone can delegate, not like a parade of mini product slogans.
Source-backed example
HubSpot calls "Send Slack notification" acceptable and "Send Slack notification by Alpha Co." unacceptable, while also requiring tool descriptions to be 50 to 150 characters and clearer than the name itself.
Source-reported evidence
Source: HubSpot Docs: Agent tool listing requirements · Browse HubSpot Docs: Agent tool listing requirements tactics
HubSpot wants tool names to begin with a verb, stay between 3 and 7 words, and pair with a 50 to 150 character present-tense description.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Marketplaces, Positioning, UX is relevant to tool naming, plain language, ui clarity and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Positioning, using evidence from HubSpot Docs: Agent tool listing requirements as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from HubSpot Docs: Agent tool listing requirements
Explore related GrowthDex examples and evidence connected to HubSpot Docs: Agent tool listing requirements.
Open HubSpot Docs: Agent tool listing requirements source hub