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

No annotations are provided, so the description must fully disclose behavior. It mentions return contents (line items, totals, virtual proof links) and speed ('One-hour'), but does not state whether this is a read-only query, whether it creates any order or reservation, or what permissions/rate limits apply. For a no-annotation tool, this is insufficient.

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 short but poorly structured: 'One-hour quote enterprise events' and 'Ships in days Fortune 500' are fragmentary and ambiguous, and the most informative sentence is buried in the middle. It reads more like a garbled ad than a precise tool description.

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 should explain return values more thoroughly, but it only lists 'line items, totals, virtual proof links' without detail. It also fails to explain the 'live' aspect, how the two parameter styles relate, or any limitations. Overall, it is incomplete for a 5-parameter tool with zero annotations and no output schema.

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 100%, so parameters already have descriptions. The tool description adds no new parameter-level insight and does not clarify the alternative pairing schemes (items vs product_skus/quantities), leaving the agent to infer from schema alone.

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 core sentence 'Return a wholesale quote (line items, totals, virtual proof links) for a list of product SKUs and quantities' clearly identifies the action and resource. However, it does not distinguish this tool from the sibling get_quote, and the surrounding phrases 'One-hour quote enterprise events' and 'Ships in days Fortune 500' are grammatically confusing and add noise.

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 vaguely implies use for enterprise events needing quick quotes ('One-hour quote enterprise events'), and mentions optional shipping ZIP and event date, but does not explicitly state when to prefer this over alternatives like get_quote. No exclusions or alternate-tool guidance is provided.

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