order_preview

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

No annotations are provided, so the description carries the full disclosure burden. 'Stage' plus 'Not an order' usefully signals an ephemeral, non-committal operation with no purchase effect, but it omits preconditions such as whether a populated cart is required or whether the address/card must already exist.

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 short sentences, front-loaded with the action and inputs, then the critical constraint. No wasted wording and no redundancy with the schema.

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 two-parameter, non-destructive preview with no output schema and no annotations, the description covers inputs and the key non-commitment property. It leaves open what the preview actually validates or returns and how it differs from checkout_preview, which matters given the dense sibling set.

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%, so the description must compensate, and it does: it explains that address_index refers to a saved address and card_suffix is the four-digit card suffix, tying both to the saved_addresses and saved_cards siblings. It still doesn't state index origin/bounds or any format validation for the suffix.

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 (stage) and resource (checkout preview) and binds it to concrete inputs, so the action is unambiguous. It does not differentiate itself from the sibling checkout_preview, which appears to serve a very similar purpose, so an agent cannot tell the two apart from the description alone.

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?

'Not an order' implies this belongs before submit_order, which is a useful implicit placement in the workflow. However, there is no explicit when-to-use statement and no guidance on choosing between order_preview and checkout_preview, so the routing decision is left to inference.

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