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

With no annotations, the description carries the full burden, and it does add real behavioral context: the quote locks only at post acceptance (so it is non-binding beforehand) and cheaper nearby slots are surfaced when the multiplier exceeds 1. It omits quote validity/expiration, currency, auth requirements, and what the response contains, and the max_price_usd reference is unverifiable against the schema.

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?

A single dense sentence with the core action and pricing condition front-loaded and no filler. The parenthetical is compact, though embedding an undefined parameter name inside it is a structural weakness.

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?

No output schema exists, and the description gives only partial return semantics (price plus cheaper nearby slots). For a pricing tool where correctness of the returned quote matters, missing details such as quote lifetime, currency, and the phantom max_price_usd leave meaningful gaps.

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 0%, so the description must compensate; it does explain that deliveries is a count N and that scheduled_at defines a 15-minute slot rather than a single instant, which is genuinely useful. But it introduces max_price_usd, a parameter absent from the schema, creating ambiguous semantics for the two documented parameters.

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?

States a specific verb (price quote) and resource (deliveries in a 15-minute slot at scheduled_at), plus the scope of N deliveries. It does not name sibling get_pricing or explain how a quote differs from a price list, so an agent must infer the distinction.

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 implies the workflow ('locks at post acceptance') and hints at guarding with max_price_usd, which tells the agent this is a pre-commitment step. However it never states when to choose get_quote over siblings like get_pricing or create_post, and 'guard with max_price_usd' references a parameter that does not exist in the input schema, muddying rather than guiding usage.

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