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

Annotations already flag non-read-only, non-idempotent, open-world behavior, and the description adds meaningful real-world consequences: a call-center operator phones the customer, then a courier delivers and collects payment. It does not discuss duplicate-order risk, cancellation, or rate limits, but the core side effects are disclosed.

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 tight sentences with the critical real-order nature, fulfillment process, and confirmation gate front-loaded. No filler.

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 the essential workflow and confirmation requirement for a consequential write operation. With no output schema, it could say more about the response (e.g., order ID) and failure behavior, but the operational picture is sufficiently complete to call it 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 75%, so most parameters are documented structurally. The description adds meaning beyond the schema by explaining that customer_confirmed=true implies the shopper explicitly confirmed product, variant, total, and phone number, which is a stronger semantic constraint than the schema's 'Must be true' note.

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 ('Places a real cash-on-delivery order') and emphasizes 'real' to distinguish it from status/query siblings. An agent can immediately tell this is the actual fulfillment action, not a lookup.

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 a clear precondition: the order is accepted only with customer_confirmed=true, which the shopper must explicitly provide after confirming product, variant, total, and phone. It does not name alternatives or exclusions, but the usage context is well defined.

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