autotask_search_companies

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

No annotations provided. The description only discloses a max page size of 200, but fails to mention pagination behavior, result ordering, search matching logic (fuzzy/exact), or authentication requirements.

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 with no redundancy. Front-loads the primary purpose and key constraint. Every word is useful.

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?

Despite being a simple search tool with no output schema, the description omits important context like pagination details beyond max size, what happens without filters, and the fact that no parameters are required.

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 low (25%), with only pageSize having a description. The tool description adds 'by name or status' but doesn't link searchTerm to name or isActive to status. The 'Max 200/page' repeats schema info. Insufficient compensation for low schema coverage.

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 action (search), resource (companies), and filters (by name or status). It distinguishes from sibling search tools for different entities, which all have similar naming patterns.

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 vs alternatives, or conditions for using filters. The description only implies usage through the action verb, but lacks explicit context or exclusions.

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