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

Annotations declare readOnlyHint=false and destructiveHint=false, so the operation is not a pure read and presumably has side effects (external provider calls, possibly cost or a persisted quote), yet the description's read-flavored 'Get' wording discloses none of that, nor rate limits, auth needs, or whether a quote is reserved/locked. It adds no behavioral context beyond the title-level statement.

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?

A single front-loaded sentence with no filler; the resource and driving inputs come first. It is efficient, though it is so terse that the brevity comes at the cost of guidance rather than through tight editing.

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?

There is no output schema and no annotation detail, and the schema marks zero required parameters, which the description never addresses (it reads as if all four inputs are needed). For a quote tool with optional inputs and a non-read-only annotation profile, some additional context on defaults and return shape would be warranted.

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% and all four parameters are documented in the schema, so the baseline is 3. The description merely re-lists the same inputs (origin, destination, weight, priority) without adding format, units, or default-value meaning beyond what the schema already provides.

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 (get shipping quotes) and names the inputs that drive the quote (origin, destination, weight, priority), which separates it from generic pricing siblings such as calculate_price or near_quote. It does not explicitly name an alternative tool or contrast with create_shipment/get_shipments, so it stops short of a 5.

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 says what the tool returns but never states when to use it versus calculate_price, near_quote, get_logistics_overview, or create_shipment, nor does it give prerequisites or exclusions. An agent must infer the routing decision entirely on its own.

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