Arrange shipment

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

Annotations already indicate destructiveHint=true, so the agent knows it's a mutation. The description adds context: 'changes live shop data' and 'requires the seller's explicit confirmation before it executes', which is valuable beyond annotations.

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 very brief: two sentences plus a critical warning. Every sentence adds value (purpose, context, critical behavior). Front-loaded with the main action.

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?

Given 5 parameters, no output schema, and destructive annotations, the description covers purpose and critical behavior but lacks parameter details. It does not explain return values or what happens after execution, leaving some uncertainty for the agent.

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 only 40% (only platform and confirmation_token have descriptions). The description does not explain the meaning of order_id, method, pickup_time, or confirmation_token, nor does it clarify the enum values for method beyond 'pickup' or 'dropoff'. It fails to compensate for low coverage.

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 a specific verb ('Book') and resource ('courier pickup or drop-off for an order'), clearly distinguishing the action from read-only siblings like 'track_shipment' or 'get_shipping_document'. It also clarifies the digital nature vs physical handover.

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 usage as the digital step before physical handover and warns that confirmation is needed, but it does not explicitly state when to use vs alternatives (e.g., when to use arrange_shipment vs track_shipment). No exclusions or when-not guidance.

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