list_companies

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

With no annotations, the description carries full burden. It discloses auto-resolve for account_id but fails to mention pagination behavior, ordering, or rate limits. The read-only nature is implied but not explicitly stated, and no side effects or prerequisites are covered.

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 concise: two sentences plus bullet-like arg descriptions. It front-loads the purpose and uses minimal, efficient wording with no redundant or filler content.

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 the output schema exists, return values are covered elsewhere. However, the description lacks details on pagination (how to navigate pages beyond per_page), ordering, and handling of large result sets. It also does not mention permissions or that it returns all companies for the specified account. The omissions reduce completeness for a list operation with pagination.

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 0%, so the description must compensate. It explains each parameter: account_id auto-resolves, per_page max 250, and status filter with common values ('active', 'disabled'). This adds significant meaning beyond the schema's type and default annotations.

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 explicitly states 'List companies (client businesses) under a CallRail account,' which clearly identifies the action and resource. It distinguishes from sibling tools like create_company, get_company, delete_company, and update_company.

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 provides no explicit guidance on when to use this tool versus alternatives, such as list_accounts or other list tools. It only mentions the scope of 'under a CallRail account' but lacks when-not or comparative context.

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