autotask_search_companies

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

No annotations are provided, so the description must fully convey behavioral traits. It discloses a pagination limit (max 200/page) but fails to mention if the operation is read-only, any required permissions, or potential side effects. This leaves the agent uncertain about safety.

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 extremely concise with only two short sentences. It front-loads the purpose and includes the key constraint. No superfluous information.

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 four parameters, no output schema, and no annotations, the description is inadequate. It does not describe return structure, error handling, or what 'status' means. A search tool with multiple filters needs more contextual guidance for an agent to use correctly.

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 only 25% (only pageSize has a description). The tool description adds context by mentioning 'name' and 'status', which loosely correspond to searchTerm and isActive, but does not elaborate on parameter formats, behaviors, or relationships. It provides some value beyond the schema but insufficient to compensate for the low 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 verb 'Search', the resource 'companies', and the filters 'by name or status'. It distinguishes itself from sibling search tools like autotask_search_services or autotask_search_contacts by specifying the target entity.

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 implicitly suggests use for company search by name or status but provides no explicit guidance on when to use this tool versus alternatives (e.g., for filtering by other criteria). It lacks when-not-to-use or alternative tool references.

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