list_companies

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

No annotations provided, so description carries the burden. It mentions account_id auto-resolves, which is behavioral, but does not explicitly note read-only nature or lack of side effects. 'List' implies read, but could be more explicit.

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?

Concise, front-loaded with purpose, followed by parameter documentation. No redundant sentences.

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?

With existing output schema, description covers parameter behavior sufficiently. While it doesn't explain pagination beyond per_page or response structure, it is adequate for a simple list operation.

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?

Despite 0% schema coverage, the description adds detailed meaning for all three parameters: account_id (auto-resolves), per_page (max 250), status (filter with common values). This compensates fully for the missing schema descriptions.

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?

Clearly states it lists companies (client businesses) under a CallRail account. The verb 'list' and resource 'companies' are specific and differentiate from single-resource (get_company) or mutation tools (create/delete/update).

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?

Provides clear context that it retrieves companies under an account, but does not explicitly state when to use vs alternatives like search_calls_by_number. However, the tool name is self-explanatory among CRUD siblings.

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