get_delivery_quote

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

Annotations only declare readOnlyHint/openWorldHint; the description goes further by stating nothing is dispatched, no money moves until acceptance, the call goes straight to DoorDash signed with the caller's local key, and no user confirmation is needed. That is substantive behavioral context beyond the structured hints.

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?

Front-loaded with purpose, behavior, and usage; the parameter glossary is compact and each line earns its place. Marginally verbose in places but no filler and the ordering is sensible.

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 endpoint with no output schema, the description covers the safety profile, the external dependency, and the primary inputs, and even names the return contents (fee, tax, ETA). The remaining gap is the set of undocumented optional parameters with defaults.

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 description coverage is 0% across 13 parameters, so the description must carry the semantics. It usefully documents 6 of them with real meaning (cents, E.164, comma-separated addresses, POS order number), but leaves contactless_dropoff, pickup_instructions, dropoff_instructions, and the contact/reference fields undefined, so it only partially compensates.

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 (quote), resource (DoorDash Drive delivery), and the concrete outputs (delivery fee, tax, ETA). It is immediately distinguishable from siblings accept_quote/dispatch_delivery because it frames itself as the non-committing pre-step.

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?

Explicitly says to 'quote liberally' with no user confirmation, and names the exact point where confirmation IS required (before accept_quote / dispatch_delivery). This is an explicit when/when-not plus the alternative tools, which is the top of the scale.

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