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

No annotations are present, so the description carries the behavioral burden. It does disclose the key behavior: returns a quote, includes virtual-proof links, and reflects shipping/timing factors. It does not fully explain what virtual-proof links are or whether the operation is read-only, which keeps it from 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 sentences: purpose, when-to-use, alternative, with no filler. Critical routing information is front-loaded in the first sentence and the contrast follows immediately.

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?

The tool has no output schema or annotations, so the description must cover return value and behavior; it does state the return kind and the conditions under which it should be used. Remaining gaps are the exact response shape and meaning of virtual-proof links, but for selecting/invoking this is adequate.

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?

All five parameters are already described 100% in the schema, so the baseline is 3. The description adds semantic weight by connecting shipping_zip and event_date to shipping/timing and characterizing items as SKUs/quantities; the only slight ambiguity is 'SKUs' vs the schema's 'slug' terminology.

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?

Description uses a clear verb ('Return') with resource ('wholesale quote with virtual-proof links') and scope ('list of SKUs and quantities, optionally ... ZIP and event date'). It names sibling get_quote and distinguishes itself by shipping/timing sensitivity, so an agent can select it confidently.

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?

Explicit 'Use when shipping or timing affects the answer' plus direct contrast with get_quote ('plain priced list with neither'). This is textbook when-to-use and alternative guidance; no inference required.

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