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

Annotations already disclose that this is a non-destructive, non-idempotent write operation. The description adds useful behavioral context beyond that: it returns the order id and total, payment is required before the pickup QR is emailed, and the QR goes to the provided email.

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 three tight sentences with no wasted wording. Creation is front-loaded, followed by return information and the payment/email follow-up.

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 simple create-order tool with no output schema, the description supplies the key return behavior and post-payment QR delivery. It does not mention every sibling workflow, but the schema covers item sourcing from get_shop and the description covers the main post-creation flow.

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 67%, and the schema itself documents email, name, item id, and qty. The description adds meaning by explaining that the pickup QR is sent to the email once paid, but it does not supplement the remaining parameter details beyond what the schema already provides.

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 states a specific verb and resource: create a pickup order to collect in person. It also distinguishes the follow-up action by naming pay_order, so an agent can separate creation from payment.

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 gives clear usage context: create an order for in-person collection, then pay it with pay_order. It does not explicitly say when not to use it or compare it to all siblings, but the workflow context is sufficient for selection.

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