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

Annotations only state the safety profile (not read-only, not destructive, closed-world); the description adds genuinely new behavior: the restoration is state-preserving ('as it was'), it is time-boxed to 1:00 AM on the pickup day, and it needs an authenticated customer session. It does not say what happens if the slot is no longer available or whether the restore can fail, so it stops short of full transparency.

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?

A single tight sentence with the core action front-loaded, followed by the deadline and auth requirement — no filler, nothing that could be cut without losing meaning.

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 mutation with no output schema, the description covers the essentials: what is restored, the hard time window, and the auth prerequisite. It is only missing the pickupId provenance and failure/edge-case behavior (expired window, unavailable slot).

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?

There is a single required parameter, pickupId, with 0% schema description coverage and no mention in the description — the agent gets no guidance on where to obtain it (e.g., list_past_pickups). The name is largely self-explanatory and the tool is single-parameter, so the gap is modest rather than blocking.

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 gives a specific verb and resource ('bring back a pickup canceled by mistake') and adds the key qualifier 'as it was', which distinguishes it from a general update_pickup by signaling restoration of prior state rather than new values. It never names a sibling tool explicitly, so differentiation is inferential rather than stated.

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?

Usage context is clear: use it for a pickup canceled by mistake, and it must happen before 1:00 AM on the pickup's day, plus it requires the customer's Happy Hamper login. There is no explicit exclusion or pointer to an alternative (e.g., what to do after the deadline, or use update_pickup to change details), which keeps it below a 5.

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