autotask_search_companies

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

No annotations provided. Description only mentions max 200 per page but doesn't disclose pagination behavior, search semantics (exact vs. fuzzy), or any side effects. Relies heavily on schema which also lacks detail.

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?

Two concise sentences conveying purpose and limit. No unnecessary words. Front-loaded effectively.

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 simple search tool, lacks details on how to formulate searchTerm, what status boolean means, pagination behavior across pages, and error/empty result handling. With no output schema, more context would be helpful.

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 25% (only pageSize described). Description adds mapping of searchTerm to 'name' and isActive to 'status', but no details on formats or valid values. Description partially compensates but insufficiently.

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?

Description clearly states verb (search), resource (companies), and filters (name or status). Distinguishes from sibling tools that search other entities like contacts or 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?

Implied usage for searching companies, but no explicit guidance on when to use this vs. other search tools or when not to use it (e.g., no mention of alternatives for company lookup like get_company).

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