Pause or resume a scheduled job

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

Annotations only say openWorldHint=false and destructiveHint=false, so they convey nothing about the side effects of the toggle. The description discloses a genuinely non-obvious behavior: resuming clears the failure count, and the job auto-pauses after ten consecutive failures. That is exactly the kind of hidden state interaction an agent needs before resuming a job. It stops short of 5 because it doesn't say whether pausing interrupts an in-flight run or whether the reset is reported back.

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?

One sentence with no padding, but it is mis-front-loaded: the leading content should be what the tool does, with the resume side effect as a trailing caveat. As written, the agent hits an unexplained detail before any statement of purpose.

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?

The tool is simple (two required params), the schema is fully described, and annotations establish it is a safe, closed-world operation, so the description doesn't need to carry much. Still, for a mutation of job state it omits whether pausing takes effect immediately for a running job, whether the call is idempotent, and what state is returned.

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 coverage is 100% and both parameters are documented inline, including that `enabled=false` pauses and `true` resumes, so the baseline is 3. The description adds a little meaning to `enabled=true` (the failure-count reset) but nothing beyond that for `enabled=false` or for the `id` parameter.

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 never states what the tool does; the purpose is only inferable from the name and title ("Pause or resume a scheduled job"). The single sentence is a side-effect footnote rather than a purpose statement, so an agent reading the description alone gets behavior, not function.

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?

There is no guidance on when to pause vs resume, no prerequisites, and no mention of siblings like add_schedule, remove_schedule, or list_schedules. The only guidance-adjacent content is the implicit warning that resuming resets the failure counter, which helps the agent anticipate consequences but doesn't tell it when to call the tool.

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