List Companies

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral details beyond annotations: it mentions the default sort order ('most-recently updated first') and the return content ('compact summaries with slug and contact_slugs values'), providing transparency about what the tool returns.

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 only two sentences, front-loaded with the primary action, and every sentence adds value: the first explains what it lists and the ordering, the second describes the return format and points to an alternative for filtered queries. No unnecessary words.

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 tool has an output schema and annotations, the description covers the key aspects: what it lists, the ordering, the return summary fields, and when to use an alternative. There are no obvious gaps that would prevent an agent from using it effectively.

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 100%, with each parameter described (page, limit, sort_by, sort_order). The description adds minimal parameter-specific meaning; it reiterates the default sort behavior already specified in the schema ('most-recently updated first' corresponds to sort_by=updatedon and sort_order=desc), but does not go beyond that.

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 tool lists all companies in the account and specifies the default ordering ('most-recently updated first'). It also distinguishes itself from sibling tool search_companies by explicitly directing filtered queries there, so there is no ambiguity about its purpose.

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 explicitly says 'Use search_companies for filtered queries,' which tells the agent when to choose this tool versus the alternative. It also implies this tool is for unfiltered listing, giving clear usage context.

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