autotask_search_companies

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

No annotations exist. Description mentions max per page (already in schema) but lacks disclosure on pagination mechanics (e.g., how to get remaining results), idempotency, or side effects. Minimal behavioral insight.

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?

Extremely concise (two sentences). No wasted words, but lacks important details like default sorting or result structure.

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 4 optional parameters and no output schema, description provides basic intent but omits return format, pagination details beyond max, and example usage. Adequate for a simple search, but not comprehensive.

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 low (25%, only pageSize). Description partially compensates by indicating searchTerm corresponds to 'name' and isActive to 'status', but does not fully explain their usage or valid formats.

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?

Clear verb 'Search' and resource 'companies', with filters 'by name or status' and constraint 'Max 200/page'. Distinguishes from sibling search tools by targeting companies.

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 use for finding companies, but no explicit guidance on when to use this vs. other search tools (e.g., autotask_search_contacts). No exclusions or alternatives provided.

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