preview_order

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

The description states 'read-only, no charge' but the annotations have readOnlyHint=false, which contradicts the claim. This is a serious inconsistency that confuses the agent about whether the tool mutates state. No other behavioral traits are described beyond the contradiction.

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 dense and runs on, making it hard to parse quickly. It lacks front-loading and could be more structured with bullet points. However, it contains useful information with minimal 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?

Despite having 8 parameters and no output schema, the description covers all critical aspects: what the tool outputs, when to rerun, parameter special cases, and budget handling. It is fully self-contained for the agent to use correctly.

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%, but the description adds significant context beyond the schema: it explains that fulfillment mutates the cart mode, no_apply_credits should only be passed on explicit user request, and priority is incompatible with pickup/scheduled_time. This greatly aids correct parameter usage.

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 provides 'Authoritative pricing + logistics for a cart' and lists specific outputs (display_summary, quote, default card). The purpose is distinct from sibling tools like submit_order or add_items_to_cart.

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 includes explicit guidance: 'Re-run after ANY cart change', when to pass include_work_benefits, and budget comparison advice. It also tells how to use specific outputs like 'display_summary (show VERBATIM to the user)'.

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