hubspot_get_active_companies

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description bears the full burden of disclosing behavioral traits. It states it returns 'most recently active companies' (implying recency-based sorting) but does not disclose read-only status, pagination behavior, or the definition of 'active'. This is partially transparent but lacks key details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that introduces the tool's main action. It is front-loaded with the verb and resource, but slightly too minimal—additional context could fit without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 optional parameter, no output schema), the description is adequate but incomplete. It omits the meaning of 'active', the expected output structure, and any side-effect information. An agent may lack enough context to use the tool correctly without external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (the single 'limit' parameter is documented in the schema as 'Maximum number of companies to return (default: 10)'), so baseline is 3. The description does not add extra meaning about the parameter, but the schema already handles it adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves 'most recently active companies' from HubSpot, specifying a verb ('Get') and resource ('companies') with a qualifier ('most recently active'). This distinguishes it from sibling tools like 'hubspot_get_company' (individual company) and 'hubspot_get_company_activity' (activity for a company), but does not explicitly clarify the meaning of 'active' or differentiate from potential similar list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, no context about usage scenarios, and no exclusions. The agent is left to infer from the name and description alone, which is insufficient for optimal tool selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.