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

With no annotations, the description carries the full burden and does well: it discloses the hard rate limit (10 calls/hour), names the return fields (carrier, service, transit days, price), and describes fallback flagging for parcel/custom-quote items. Gaps remain around auth/prerequisites and error behavior for invalid or non-US ZIPs, keeping it below 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 tight sentences, front-loaded with the core capability before the return fields and the rate-limit caveat. Every sentence conveys distinct information (what, output, constraints/edge cases) with no redundancy.

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 compensates by enumerating return fields and surfacing the rate limit and flagging behavior, and params are fully covered by the schema. Only minor gaps remain: it doesn't clarify auth requirements or what form the 'flagged' signal takes in the response.

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% (zip, items, sku, qty, liftgate, residential all documented inline), so the schema already carries parameter meaning. The description adds only that items are 'to ship' and implies the multi-product shape, which is baseline value rather than new semantics.

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+resource (fetch live LTL freight rates) with scope (US ZIP, one or more products) and explicitly says it uses real carrier pricing, the same engine as checkout. This clearly distinguishes it from siblings like search_products, get_product and create_quote_request, which deal with catalog data or quote creation rather than live rate lookups.

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?

Usage is implied: get live rate estimates for a shipping destination. The note that parcel-eligible and custom-quote items are 'flagged' hints at alternate paths (UPS parcel, custom quote) but never explicitly names create_quote_request or states when to prefer it. No explicit when-not guidance, so it lands at implied usage rather than actionable routing.

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