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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=true), so the description earns credit for adding behavior beyond them: schedule runs stop entirely until resumed, and the operation bypasses an approval step. What it does not clarify is what happens to a run already in flight or how long the paused state persists, which keeps it short of a 5.

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 very short sentences, each carrying distinct information: the action, the runtime consequence, and the approval requirement. The action is front-loaded and there is no filler.

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 state-toggle with full schema coverage and annotations covering safety and idempotency, the description supplies what structured fields cannot: the effect on scheduled execution and the absence of an approval gate. Only edge-case behavior (in-flight runs, resume path) is left unstated, which is a minor gap at this complexity.

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 schema already says the parameter is "The schedule to pause (from list_schedules)." The description adds nothing about the identifier's format or source, so it sits at the baseline for fully documented single-parameter schemas.

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 uses a specific verb and resource sequence: "Switch a schedule off," followed by the consequence "Nothing runs until it is resumed." That makes the operation's direction clear (opposite of resume_schedule), though it never names the sibling explicitly, so differentiation is implied 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 is implied by the effect statement ("Nothing runs until it is resumed"), which tells the agent the outcome of pausing, and the phrase "Needs no approval" hints that no approval workflow is required first. However, there is no explicit when-to-use framing versus siblings like set_schedule or resume_schedule, and no stated preconditions.

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