Place order

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description's added value is the failure conditions ('fails if the preview does not exist or has expired') and the human-confirmation gate, which an agent would otherwise not know. It stops short of describing resulting order state or how duplicate submissions behave, so not a 5.

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?

Three short sentences: what it does, the required human confirmation, the sequencing prohibition, and the failure mode. No filler, and the prerequisite is front-loaded.

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 single-parameter mutation with no output schema and annotations covering the safety profile, the description supplies everything an agent needs: the source of the ID, the confirmation gate, the ordering constraint relative to preview_order, and failure conditions.

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 the single preview_id is documented in the schema, so the baseline is a 3; the description adds meaning by tying the ID to preview_order and declaring that stale/nonexistent preview IDs cause failure, which is a real validity constraint beyond the schema.

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 and resource ('place an order') and ties it directly to its generating sibling ('from a preview made by preview_order'), which cleanly separates it from preview_order and cancel_order without needing the schema.

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?

Gives an explicit precondition (user must have explicitly confirmed the preview, with example affirmations), an explicit prohibition ('never call it in the same step as preview_order'), and the alternative to use first (preview_order). Nothing 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.