get_shipment_providers

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

With no annotations, the description carries the behavioral burden, and 'List' does signal a read-only listing operation. It also surfaces a non-obvious output behavior (per-provider tracking-code requirement), but it does not explicitly address side effects, permissions, or failure behavior, which a full-burden description would ideally include.

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 compact sentence front-loads the core operation and packs the conditional routing into a parenthetical. There is no filler or redundant restatement of the tool name.

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 one-parameter listing tool with no output schema, the description covers the operation, the parameter context, and the key output trait (whether tracking code is caller-supplied). It is complete enough to call correctly, though it does not describe response shape or edge cases.

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?

The description adds key semantic context by saying the tool lists providers 'for an order item', which clarifies that order_item_id identifies the order item in question. It does not provide format or source details beyond that, but for a single self-descriptive parameter this is adequate.

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 uses the specific verb 'List' with a precise resource, 'shipment providers available for an order item', immediately identifying the operation. It also distinguishes itself by adding the tracking-code requirement and naming pack_orders_v2 as the alternative, so an agent can tell it apart from sibling tools like pack_orders.

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 parenthetical '(use pack_orders_v2 if so)' explicitly names the sibling tool and states the condition that should send the agent there. This gives clear when-to-use guidance relative to the alternatives rather than leaving it to inference.

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