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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=true, so the safety profile is covered. The description adds the connected-account auth requirement and the pauseUntil semantics ('omit to pause until resumed'), which is useful context, but it never spells out what cancel actually destroys or whether it is recoverable — the destructive behavior is left entirely to the hint.

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 compact sentence that front-loads the prerequisite before listing the actions. Every clause earns its place, with no redundancy against the schema or title.

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 three-parameter mutation tool with no output schema, the description covers the actions, the required account context, the ID source, and the pause date semantics. The remaining gap is the consequence of cancel, which the destructiveHint annotation partially covers.

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 only 33% (recurringId is undocumented), so the description carries real weight: it explains the pauseUntil date format and the 'omit to resume' behavior, and tells the agent that recurringId comes from get_my_account. It adds meaning beyond the bare enum and schema types, though the recurringId format itself remains unstated.

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 names a specific verb set (pause/resume/cancel) and resource (recurring pickup), matching the title. It is clear what the tool does, though it never explicitly distinguishes itself from the sibling set_recurring_pickup, leaving the agent to infer that this one mutates an existing recurring pickup rather than creating one.

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?

'Requires the connected Fold account' states a prerequisite, and 'recurringId from get_my_account' tells the agent where the ID comes from, which is genuine routing guidance. However, it never says when to choose this tool over set_recurring_pickup, cancel_order, or reschedule_order, so the usage context is only implied.

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