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

With no annotations, the description carries the full burden and does so well: it discloses the asynchronous human-in-the-loop fulfillment, the ~1 business day turnaround, the return value (quote number), and a hard rate limit of 5/hour. It also flags the precondition that real name and email must be confirmed with the customer, which is exactly the kind of non-obvious behavioral constraint an agent needs.

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?

Five tight sentences, front-loaded with what the tool does, followed by when to use it, the precondition, the return value, and the rate limit. No filler or repetition of the tool name.

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 6-parameter, no-annotation mutation tool, it covers purpose, trigger, prerequisites, output and rate limits, and there is no output schema demanding explanation. It could be more complete by routing agents elsewhere for immediate pricing or by noting what happens on a duplicate request, but nothing essential is missing.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining that the quote is priced by volume plus freight and that name/email must be genuine and customer-confirmed. It says nothing about how items are interpreted or what message should carry (destination ZIP, timeline), leaving those to the schema.

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 ('Create a real quote request') plus the system it lands in (MaterialHandling.com sales system), which clearly separates it from read-only siblings like search_products, get_product and get_freight_estimate. An agent can tell instantly that this is the submission/intake path, 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?

'Use when the customer wants formal/volume pricing' gives a clear trigger condition, and the described workflow (human specialist prices it, quote emailed in ~1 business day) implies the boundary against instant self-serve estimate tools. It never names an alternative sibling or states an explicit when-not-to-use case, so it falls short of a 5.

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