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

Annotations already declare this is a non-destructive write; the description adds useful context beyond them: a Happy Hamper login is required and the booking must not proceed before the customer approves the quoted price. It stops short of saying whether the booking charges a card, whether it is cancellable afterward (cancel_pickup exists), or what confirmation is returned.

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 sentences, front-loaded with the core action and then the prerequisites, with no filler. The opening is a telegraphic fragment ('One pickup on a date') rather than a complete statement, which costs a point but not usability.

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 mutation tool with no output schema, the description should describe what the caller gets back (a booking confirmation, pickup ID, charged amount) and cover the two undocumented optional parameters. Auth and price-approval preconditions are covered, but the return behavior is left entirely unspecified.

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 67%, so most parameters are already documented in the schema (bags tiers, date format, express surcharge). The description's reference to 'the price' only loosely hints that bags maps to 1-bag/2-bag pricing, and it adds nothing about discountCode or dropoffAddressId, which lack schema descriptions.

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 the resource precisely ('One pickup on a date'), which distinguishes it from subscription siblings like start_subscription and from update_pickup/cancel_pickup. The verb is only implied by the tool name rather than stated in the description, so it falls just short of a full verb+resource statement.

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 an explicit prerequisite chain: quote_one_time_pickup first, then customer approval of the price. That is concrete sequencing with a named sibling. It does not, however, state when NOT to use it (e.g., recurring service should go to start_subscription).

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