hubspot_search_contacts

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as rate limits, authentication requirements, read-only nature, or error handling. The description only states it searches and supports filtering without additional context.

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 two sentences, front-loading the purpose and including a key feature. Every word earns its place with no redundancy or waste.

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 complexity of the search tool (6 parameters, nested filter objects) and no output schema, the description is adequate but lacks details on return format, pagination behavior, or handling of edge cases. It could be more complete to fully inform an AI 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?

Schema description coverage is 67%, meaning many parameters already have good descriptions in the schema (e.g., 'query', 'filters'). The description adds only high-level context ('by email, name, or other properties'), which adds some value but does not significantly enhance understanding beyond the schema.

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', resource 'contacts in HubSpot', and specifies searchable properties (email, name, other properties). It distinguishes itself from siblings like hubspot_get_contact and hubspot_list_contacts by mentioning advanced filtering.

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 queries via 'Supports advanced filtering with multiple operators' but does not explicitly state when to use this tool vs alternatives like hubspot_get_contact for a specific ID or hubspot_list_contacts for simple listing. No exclusions or prerequisites are given.

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