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

Annotations already mark this as destructive and not read-only; the description adds meaningful behavior beyond that: only one pickup is cancelled, the subscription continues, the charge cutoff is 8:00 AM, and customer login is required.

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?

Three short, front-loaded sentences with no filler. The scope, charge policy, and auth requirement each earn their place.

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?

Provides enough high-level context for a simple cancellation, including charge timing and login requirement. However, it omits how to obtain the required pickupId and does not describe the confirmation or result, and no output schema fills that gap.

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 0% and pickupId is undocumented in both schema and description. The phrase 'one upcoming pickup' implies the parameter selects a pickup, but it gives no ID format, source, or lookup guidance.

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: cancel one upcoming pickup. The parenthetical clarifies scope by noting the subscription carries on, distinguishing it from subscription-level changes and from uncancel_pickup.

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 usage context: use before 8:00 AM to avoid a charge, and a login is required. It does not explicitly compare against alternatives such as update_pickup or state when not to cancel.

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