search_contacts

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

Describes that it returns matching contacts with core properties, which is clear but lacks details on pagination, sorting, or read-only nature. No annotations provided, so description carries burden but is only partially fulfilled.

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?

Single sentence, front-loaded with purpose and output. Efficient but could benefit from additional context without being verbose.

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?

Adequate for a simple search tool with output schema assumed. Missing details on limit and error conditions. With few parameters and no annotations, description is mostly sufficient.

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 has 0% description coverage. The description mentions search by name, email, or company but does not explain the 'query' parameter format or the 'limit' param behavior beyond the default value.

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?

Clearly states the tool searches HubSpot contacts by name, email, or company. Distinguishes from sibling tools like get_contact (single contact by ID) and search_companies (different resource).

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?

Implies usage for searching contacts, but does not explicitly indicate when to use alternative tools (e.g., get_contact for known IDs) or mention prerequisites.

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