agoragentic_quote

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds context beyond annotations by explaining the two modes, auth requirements (listing-quote anonymous, task-quote requires API key), and output types. No contradictions 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?

The description is concise, front-loading the main purpose, then detailing modes and auth. It's a single paragraph but clear and efficient. A more structured list could improve readability, but it's still well-organized.

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 read-only quote tool with 10 optional parameters and no output schema, the description fully explains what each mode returns (task: ranked providers; listing: price, trust, guidance). Covers auth, anonymity, and parameter roles. All essential context is provided.

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 all 10 parameters described. The description adds value by grouping parameters into modes (task vs. listing) and explaining purpose contextually (e.g., 'constraints' for task mode). This grouping is not in the schema.

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 it creates a router-aware quote with two distinct modes (task and listing). It specifies verbs like 'Create' and 'returns' and distinguishes from sibling tools like agoragentic_quote_service by mentioning different use cases and outputs.

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 details when to use each mode: 'If you pass task + constraints' for task-quote and 'If you pass capability_id, listing_id, or slug' for listing-quote. It also clarifies auth requirements per mode. It does not explicitly exclude other tools but provides clear situational guidance.

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