autotask_search_companies

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

No annotations provided, but description discloses default page size (25) and pagination behavior. However, lacks info on whether search is case-sensitive, supports wildcards, or any rate limits.

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?

Description is brief (two sentences) and front-loaded with main purpose. Could be slightly more efficient by combining ideas, but no extra fluff.

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 simple tool with full schema coverage and no output schema, description provides core pagination detail but misses behavioral context like default behavior when optional filters are omitted.

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. Description doesn't add meaning beyond schema; for instance, 'pageSize' max 200 is in schema but not reiterated.

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 for companies in Autotask and returns results paginated. It distinguishes from sibling search functions by focusing on 'companies' as the 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?

No guidance on when to use this tool versus alternatives like autotask_search_contacts or autotask_search_tickets. Doesn't specify that it only searches by name and active status, or mention any limitations.

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