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

Annotations declare destructiveHint=true and idempotentHint=false, yet the description frames all three actions as benign, giving no indication that pausing may interrupt in-flight work or that repeated 'run' calls create duplicate executions. It does not strictly contradict the annotations, but for a destructive, non-idempotent mutation it adds no behavioral context at all.

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 short, front-loaded sentence with no filler; the action triad is enumerated efficiently. It is perhaps too terse given the tool's mutation semantics, but nothing is 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 three-required-parameter mutation tool flagged destructive and non-idempotent, with no output schema and a poorly documented 'id' parameter, the description leaves too much unsaid about effects, reversibility, and what the call returns.

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%: only agent_id is documented. The required 'id' parameter is never explained in the description (it is presumably a duty id, but this must be inferred), and the action enum's three values are self-evident from the schema, so no added meaning is supplied where it is needed.

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 resource (a duty) and three concrete operations (run now, pause, resume), which is more informative than the title alone. It does not explicitly distinguish itself from siblings like save_duty or get_duties, but the action verbs make the operation legible.

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 choose this tool over save_duty or get_duties, nor any preconditions (e.g. whether the duty must already exist or be scheduled). The word 'now' weakly implies immediate execution versus scheduling, but no alternative or exclusion is stated.

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