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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds substantial context beyond them: the effect is stock-increasing and irreversible from this tool, and confirming an arrival that never happened conceals a loss rather than recording one. It also constrains the operation to a receive-transfer leg still in-transit.

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?

Opens with the action and its effect, then front-loads the merchant-confirmation warning before the mechanical detail. Every sentence carries a distinct piece of information — effect, risk, precondition, ID source, applicability — with no filler.

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, no-output-schema mutation with annotations covering the safety profile, the description supplies everything an agent needs: the state change, the irreversibility, the required human confirmation, the correct identifier, and the in-transit precondition.

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% and the schema already states the parameter is the stockTransferId from get_stock_transfer and not the transactionId, so the description largely restates it. It adds minor value by tying the ID source to a sibling tool, but the schema carries the parameter documentation. Baseline 3 applies for a fully covered single parameter.

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 ('Confirm that a transfer arrived'), the resource (stock transfer), and the concrete state change (destination outlet gains units, transfer closes). This cleanly distinguishes it from siblings such as hub_create_stock_transfer, hub_receive_purchase_order, and hub_record_received_goods 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?

Explicit when-to-use ('only do it when they say the goods are physically there'), an explicit prerequisite ('CONFIRM WITH THE MERCHANT FIRST'), and an explicit when-not ('a transfer already completed has nothing left to receive'). It also names hub_get_stock_transfer as the source of the ID, giving the agent a clear entry point.

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