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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and this is a pure calculation, so the safety profile is fully covered. The description adds that the result is an estimate with a formula and note, but that overlaps with the output schema rather than revealing new behavior such as whether rates are region-specific or fixed.

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?

Two short sentences, front-loaded with purpose before the return shape and pointer. The explicit return-shape listing is largely redundant given a declared output schema, which is minor waste but not bloat.

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 an output schema present, the description need not explain return values, and inputs are fully covered by the schema. The main gap is the absence of sibling differentiation among the numerous related shipping and cost tools.

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 weight_kg, distance_km and the standard/express enum are already documented with units and defaults. The description restates the same three inputs without adding format, unit, or boundary semantics beyond what the schema provides, so the baseline of 3 applies.

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 (estimate) and resource (shipping cost) and names the driving inputs (weight, distance, service level). However, it does not distinguish itself from clearly related siblings like calculate_international_shipping or calculate_shipping_volumetric, leaving an agent to guess which shipping calculator applies.

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?

There is no when-to-use framing and no exclusions or alternatives among the many shipping/cost siblings. The only pointer is to list_bundles, which is a browsing aid rather than routing guidance between competing tools.

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