doordash_checkout

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

The description discloses the key behavioral distinction between preview (confirm=false) and placing the order (confirm=true). With no annotations, this is adequate for a single-parameter tool, though it does not mention side effects like cart clearing.

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 two sentences, front-loaded, and every word adds value. No wasted text.

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?

Given no output schema, the description should explain what the preview returns, but it does not. The tool's behavior is clear, but completeness suffers from missing return value 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?

Schema coverage is 100% and description restates the schema's explanation of the 'confirm' parameter without adding new information. Baseline score is appropriate.

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 the tool's purpose: 'Proceed to checkout and optionally place the order.' It distinguishes from sibling tools (e.g., doordash_add_to_cart, doordash_cart) by focusing on the checkout action.

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 provides explicit usage guidance: 'Set confirm=false to preview order details, confirm=true to actually place the order.' It clearly explains the two modes without requiring additional context.

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