list_customers

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

No annotations provided; description lists parameters but lacks extra behavioral details like permissions, rate limits, or side effects. Adequate but minimal.

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 title sentence followed by bullet-like Args. Slightly verbose due to full param explanations, but front-loaded and clear.

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?

Covers purpose, all parameters with defaults, and uses output schema (not shown) for return values. Complete for a listing tool without needing sorting details.

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?

0% schema description coverage, but the description's Args section adds detailed meaning for all parameters (type, format, defaults, behavior), fully compensating.

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?

Specific verb 'list' and resource 'customers' with clear scope 'who have access to a service desk'. Distinguishes from sibling tools like add/remove customers.

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 context on optional filtering and pagination, but does not explicitly state when to use vs alternatives. Still clear from purpose and sibling names.

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