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

Goes well beyond the annotations by disclosing the monetary side effect ('Spends money for every label'), the return payload (per-shipment cost/tracking, total, print link), the downstream effect (tracking sent back to the store), the default confirmation behavior and its toggle, and the API-key requirement. This is exactly the behavioral context a costly, open-world mutation needs.

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?

Front-loaded with the action and the money consequence, then side effects and confirmation behavior. Most sentences earn their place; 'like Buy Labels' is slightly redundant but serves as a sibling anchor.

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?

No output schema exists, yet the description explains the return contents (per-shipment cost/tracking, total, print link) and the side effects, so an agent has enough to invoke it. It stops short of describing partial-failure behavior for a multi-label spend, a minor gap for a batched financial action.

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 the schema already documents batch_id, service, and ship_date (including that service comes from get_batch_rates and batch_id from create_batch). The description adds the nuance that one service applies to the whole batch, but otherwise the schema carries the semantics; baseline 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 and resource ('Buy labels for every shipment in a batch with one service') and explicitly contrasts itself with the sibling 'Buy Labels'. An agent can tell it apart from pirate-ship_buy_label and pirate-ship_get_batch_rates without opening any schema.

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?

Gives clear operating context ('Spends money for every label in the batch at once', confirm each call, confirm with user) and implies the batch-selection condition. It does not, however, explicitly state when to choose this over pirate-ship_buy_label for individual labels, leaving one routing decision to inference.

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