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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds no behavioral context beyond restating the boolean mapping found in the schema — it doesn't explain why the operation is flagged non-idempotent, whether pausing aborts queued messages, or whether resume replays missed runs. Given a destructive-flagged mutation, this is a thin disclosure.

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 front-loaded sentence that states both directions of the toggle with zero filler. Nothing is buried or wasted.

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 simple two-parameter toggle with full schema coverage and annotations covering the safety profile, the description tells the agent everything needed to call it correctly. Only the side effects of resuming a paused schedule are left unstated, which is a minor 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 100% and the 'active' parameter already documents 'false pauses, true resumes' — the description repeats that verbatim rather than extending it. Baseline 3 applies since the schema carries all parameter meaning.

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?

Names a specific pair of actions (pause/resume) on a specific resource (recurring schedule), and usefully narrows the otherwise-generic 'update_schedule' name to exactly these two state transitions. An agent can distinguish it from create_schedule, delete_schedule, get_schedule, and the automation/batch pause siblings without opening any schema.

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 implies usage by mapping the boolean value to each effect, but it never states prerequisites (schedule must already exist), when to prefer this over delete_schedule, or what happens to in-flight scheduled sends. It's adequate for a two-state toggle but offers no explicit when/when-not guidance.

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