hubspot_search_deals

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

No annotations are provided, so the description bears full responsibility. It mentions 'advanced filtering' but omits critical behavioral details like read-only nature, pagination behavior, rate limits, or error handling. The description lacks context on what the user should expect in terms of side effects or limitations.

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 concise with two sentences, front-loading the core purpose and key differentiator (advanced filtering). Every sentence serves a purpose without redundancy.

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, advanced filtering) and no output schema, the description is too brief. It fails to explain return format, pagination, error handling, or provide usage examples. The description is incomplete for effective agent use.

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?

With schema description coverage at 67%, the baseline is 3. The description adds minimal value beyond the schema, only listing example properties (name, stage, amount) without detailing parameter usage or operators. It does not compensate for the 33% of parameters that lack schema descriptions.

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 verb 'Search', the resource 'deals in HubSpot', and specifies searchable properties like name, stage, amount. It effectively distinguishes from sibling tools like 'hubspot_list_deals' by emphasizing advanced filtering and multiple operators.

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 implies usage for advanced filtering but does not explicitly state when to use this tool over alternatives like 'hubspot_list_deals'. No guidance on when not to use or prerequisites is provided.

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