chipotle_checkout

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

No annotations provided. Description reveals dual mode (preview vs place) via confirm flag, but lacks details on side effects like payment, cancellation, or irreversible actions. Adequate but not comprehensive.

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?

Two sentences, front-loaded with purpose, followed by critical confirm parameter guidance. No redundancy or fluff.

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 key behavior and confirm flag, but missing details on return values (since no output schema) and conditional requirements like delivery address. Adequate for a checkout tool but could be more thorough.

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 has 100% coverage with descriptions. The tool description adds context about confirm's behavior (preview vs place), but adds little to other parameters beyond what schema already provides. Baseline 3 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?

Description clearly states the tool's action (checkout/place order) and resource (Chipotle order), distinguishing preview vs actual placement. Differentiates from siblings like chipotle_view_bag or chipotle_start_order by naming the final 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?

Provides clear guidance on using confirm=false for preview and confirm=true to place. Does not explicitly mention prerequisites or alternative tools, but the context implies it's the final step after building an order.

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