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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces this with 'Nothing is purchased by this tool.' It adds real beyond-schema behavior: shipping is free from $150 else $39.90, and it returns a checkout link rather than completing a sale. No contradictions.

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 tight sentences, front-loaded with the action and the non-purchase clarification, followed by concrete pricing/return details. Every clause carries information.

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?

With no output schema, the description steps in to enumerate what comes back (total units, subtotal, shipping rules, estimated retail value, delivery estimate), which is exactly the missing return-value context. Nothing essential for correct invocation is absent.

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 reported as 0% (the nested items fields have only terse descriptions), so the description must compensate. It clarifies the critical unit semantic ('quantities are in cases'), but says nothing about the 'handle' format or how items are keyed, leaving a gap.

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 ('Price a wholesale order') and the concrete output ('return a checkout link to celadonbeauty.com'), which is clearly distinct from the sibling tools that all look up products or terms. An agent can tell this is the quoting/checkout step without opening 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?

It makes the context of use clear ('quantities are in cases', buyer reviews and pays, 'Nothing is purchased by this tool'), which tells the agent this is a pre-purchase quote step. It does not explicitly name alternatives or exclusion conditions, but the workflow position is unambiguous.

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