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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the risk profile is covered. The description adds a genuinely non-obvious trait not captured by any hint — that the request waits for the owner's approval — which materially changes how an agent should sequence work. It stops short of describing cost or duplicate-pickup behavior.

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?

Two short sentences, front-loaded with the action and the key behavioral caveat. The phrase 'like Schedule a Pickup' largely restates the tool title and is mild padding.

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 destructive, open-world, 10-parameter mutation, the agent still knows what it does, which carriers it targets, and that execution is gated on owner approval — the single fact most likely to cause a wrong call if absent. Fine-grained parameter semantics are handled by the schema.

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 60%, and the description contributes nothing about parameters beyond naming the two carriers, which the enum already encodes. The 'UPS only' semantics for date, close_time, ready_time, and overweight live entirely in the schema, so the description neither compensates for the coverage gap nor adds value.

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 ('Ask USPS or UPS to collect your packages'), making the action unmistakable. It does not explicitly name differentiating siblings such as list_pickups, cancel_pickup, or get_pickup_quote, so an agent must infer the distinction from the bare name.

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 mention of carriers and the approval wait implies when this applies, but there is no explicit when-to-use or when-not guidance. It never routes the agent to get_pickup_quote for pricing or cancel_pickup for reversals, which are directly relevant siblings.

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