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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses the chargeable-weight rule (max of gross versus volumetric) and that weight breaks plus fuel/security surcharges are applied, which is real context beyond the schema. However, it does not describe rate validity, currency, error behavior, or whether the quote is deterministic, so behavioral transparency remains partial.

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 sentences with no wasted words. The purpose is front-loaded, followed immediately by the key computation and surcharge behavior. Every sentence earns its place.

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?

The description is adequate for a tool whose input schema is fully documented, and it explains the core rating behavior. But with no annotations and no output schema, it should do more to describe the returned quote (per-kg versus total, currency, validity) and any failure conditions. An agent can call it, but cannot fully predict 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%, so the baseline is 3 even without additional parameter detail. The description adds value by explaining how weight_kg and volume_cm3 interact through chargeable weight and by framing origin/destination as a lane. That semantic linkage goes beyond the field-level schema descriptions.

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 description states a specific verb and resource: get an all-in per-kg air-freight rate quote for a lane. It is clearly distinct from the sibling tools (resolve_awb_prefix, track_awb), which handle AWB prefix resolution and tracking rather than rating. It could be slightly sharper about the quote's output form, but the purpose is unambiguous.

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 implies a rating use case but gives no explicit when-to-use guidance, prerequisites, or exclusions. It does not say when volume should be supplied, whether quotes are lane-only versus shipment-specific, or what to do if a lane is unsupported. With no sibling quote alternative, the gap is mostly about preconditions rather than tool selection.

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