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

The description adds useful behavioral context beyond annotations: it calls an external live carrier API, returns carrier HTTP request/response bodies, and writes LabelLog entries. This aligns with openWorldHint=true and readOnlyHint=false, and the write side effect is especially valuable to disclose.

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?

The description is three focused sentences, front-loads the action and resource, and each sentence contributes useful information: purpose, prerequisite, and observable behavior.

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 debug tool with no output schema, the description says enough about what it does, what it returns, and what side effect it has. It does not cover failure modes or external API constraints, but annotations and schema already carry the safety and parameter details.

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 three parameters are already documented in the schema. The description adds only contextual prerequisite information about the shipment draft, not parameter-specific meaning beyond what the schema 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?

The description states a specific action and resource: call the carrier live rates API for an existing shipment draft. It is clear and distinct from generic rate or label tools, though it does not explicitly name a sibling alternative.

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?

It implies the debug use case and states a prerequisite that a carrier contract and product must already be selected in the draft's Shipping snapshot. However, it gives no explicit when-not-to-use guidance or comparison to sibling investigation/rate tools.

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