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

Adds details beyond annotations: status pending_payment, idempotent per inquiry, return fields (order id, order_no, payment next_step), mandate authorization behavior. No contradiction with 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?

Single paragraph, front-loaded with main action, followed by parameter details and behaviors. No redundant sentences; every sentence adds value.

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 all aspects: action, parameters, prerequisites, return values, and authentication. No output schema, but description sufficiently explains 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?

Despite 100% schema coverage, description adds context: explains origin of inquiry_id and quote_id, optional mandate_id usage, and effects on response. Provides meaningful guidance beyond 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?

The description explicitly states the tool's action: 'Accept a supplier quote and create an order (status pending_payment) for one of your inquiries.' It distinguishes from siblings by referencing related tools like list_quotes and create_payment_mandate.

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?

Clear instructions: pass inquiry_id and chosen quote_id, optionally mandate_id. States idempotency and authentication requirement. References sibling tools for parameter sources.

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