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

Annotations already declare destructive, idempotent, non-read-only, open-world behavior; the description goes beyond them by naming the idempotency mechanism (requestId reuse on retry), the optimistic-concurrency requirement (current version), and the permission scopes enforced. It stops short of saying what a pause does to already-scheduled work or whether the change is reversible.

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 sentences, front-loaded with the core action and effect, followed by retry and prerequisite details. Every sentence carries information; only minor tightening would help.

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, non-read-only mutation with no output schema and 0% schema coverage, the description covers idempotency, concurrency control, and permission enforcement, which is most of what an agent needs. The gap is the absence of any statement about reversibility or post-pause state, which matters given destructiveHint=true.

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%, so the description must carry all four parameters. It explains requestId (unique, reused on retry) and version (must be the current version from get_tasks/get_items/get_workspace), and 'pause or resume' maps to the paused boolean, but the id field's meaning (schedule vs item identifier) is left 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?

States a specific verb+resource: 'Pause or resume a recurring task schedule', and scopes the effect to future task creation and configured reminders. It does not, however, name or contrast itself against the nearby schedule_save sibling, so the agent still has to infer which schedule tool to pick.

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 description supplies prerequisites and retry guidance (reuse the same requestId when retrying, fetch the current version first), which implies correct usage. It never states when to choose this tool over schedule_save or rule_toggle, so no explicit when/when-not routing is provided.

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