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

Annotations only declare destructiveHint=true and idempotentHint=false; the description goes well beyond by spelling out the two-step confirm flow (first call returns a summary and confirmToken, second call with the token proceeds) and the concrete side effect that overdue entries write on the next run and publish immediately. This is exactly the context needed to invoke a destructive tool safely.

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 short sentences with zero filler, front-loading the core action and the destructive confirm requirement before the optional reschedule guidance. Every clause carries operational meaning.

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?

With no output schema, the description usefully explains that the first call returns a summary plus token, and it discloses the publishing side effect of resuming. Minor gaps remain (e.g., what happens if the token is never supplied), but nothing critical for correct invocation is missing.

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%, so both site and confirmToken are already documented in the schema itself. The description restates the confirmToken handshake but adds no new syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 (resume) plus the resource and effect (automatic writing and publishing), and anchors it to the sibling state it reverses (after pause_autopilot). An agent can distinguish this from pause_autopilot or reschedule_overdue 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?

Clearly conditions usage on a prior pause_autopilot and names a precondition alternative ('call reschedule_overdue first if they should be spread out'), which is genuine when/when-not guidance. It stops short of stating any exclusion for when NOT to resume at all, so it is strong but not exhaustive.

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