hubspot_search_companies

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

No annotations are provided, and the description fails to disclose behavioral traits such as whether the operation is read-only, rate limits, authorization requirements, or pagination behavior. The description simply states the capability without any transparency beyond the input schema.

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 remarkably concise with two sentences, no wasted words, and the primary verb and resource are front-loaded. Every word contributes to understanding the tool's purpose, making it highly efficient.

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 complexity (6 parameters, nested filters) and absence of an output schema, the description is too brief. It omits details about pagination, result format, and limitations. A more comprehensive description is needed to fully inform the agent.

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?

The description adds minimal value beyond the input schema, which already covers 67% of parameters with descriptions. The mention of 'by name, domain' provides context for the query parameter, but does not compensate for missing descriptions of limit and properties. Overall, the description does not significantly enhance parameter understanding.

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 action ('search') and the resource ('companies in HubSpot') with criteria options ('by name, domain, or other properties'). It effectively communicates the core purpose, though it does not explicitly differentiate from sibling search tools for other object types.

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 does not provide guidance on when to use this tool versus alternatives such as `hubspot_get_company` or `hubspot_list_companies`. It implicitly suggests usage for flexible search but lacks explicit when-not-to or context for decision-making.

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