autotask_search_contacts

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

No annotations are provided, so the description carries the full burden. It only mentions 'Max 200/page,' indicating a pagination limit, but lacks other behavioral details such as read-only status, authentication requirements, or rate limits. For a search tool, minimal disclosure.

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 a single concise sentence with no superfluous words. It efficiently conveys the core purpose and a key constraint (max 200 per page).

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?

For a search tool with 5 parameters and no output schema, the description covers the basic purpose and search criteria but lacks details on return format, pagination behavior (e.g., how to get next page), or error handling. It is minimally complete given the tool's simplicity.

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 80%, so baseline is 3. The description adds value by naming searchable fields (name, email, company), which correspond to 'searchTerm' and 'companyID', but does not explain 'page', 'pageSize', or 'isActive' beyond what the schema already provides. Limited additional semantic 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?

The description clearly states 'Search contacts by name, email, or company,' specifying the verb (search), resource (contacts), and key search criteria. It distinguishes this tool from sibling tools like autotask_search_companies or autotask_search_tickets by explicitly targeting contacts.

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 searching contacts, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., autotask_create_contact for creation) or when not to use it. No exclusions or preconditions are mentioned.

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