List Companies

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds that it returns a paginated JSON array, includes pagination metadata, and provides the exact endpoint URL. Effectively communicates behavior without contradicting annotations.

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?

Every sentence adds value: purpose, header note, usage suggestion, pagination detail, endpoint reference. No wasted words. Well-structured for quick consumption.

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?

For a simple list tool with comprehensive annotations, the description covers the essential: purpose, usage, pagination, and endpoint. No output schema, but the tool is straightforward. Minor gap: no mention of response fields.

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 already covers all three parameters with descriptions (100% coverage). Description repeats 'use page and per_page to control pagination' but adds no new semantics beyond what schema provides. Baseline of 3 is appropriate.

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 'Return a list of Companies visible to the User' with specific verb and resource. It distinguishes itself from sibling tools by mentioning pagination, filtering, and the header requirement note. The title matches.

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 explicit usage context: 'Use this to enumerate Company Settings when you need a paginated overview, to find IDs, or to filter by query parameters.' Also notes the header not required. However, does not explicitly exclude alternatives or compare to sibling tools like listing vendors or projects.

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