autotask_search_contacts

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

With no annotations, the description should convey behavioral traits beyond the schema. It only notes a page limit of 200, which duplicates the schema's maximum. It omits details like whether results are paginated, the return format, or any read-only nature, leaving the agent uninformed.

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 very concise with two clear phrases, front-loading the purpose. Every word earns its place, though it could be slightly more structured with separate sections for criteria and limits.

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?

The description is insufficient given the tool's 5 parameters, lack of output schema, and many sibling search tools. It does not explain return values, pagination behavior, or how to handle multiple pages, leaving the agent with significant unknowns.

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 coverage is high (80%), and the description adds value by mapping searchTerm to name/email and companyID to company. However, it does not explain the 'page' parameter or the 'isActive' filter, missing a chance to fully compensate for the schema gaps. Baseline 3 is appropriate.

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 searches contacts by name, email, or company, which is a specific verb-resource combination. It naturally distinguishes from sibling search tools like autotask_search_companies and autotask_search_tickets.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., autotask_search_companies for company searches or autotask_get_contact for a single contact). The description lacks explicit context for selection.

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