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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses a non-obvious behavioral rule: the pause days are not caught up, the restart begins today. It also spells out the two-phase preview/execute contract and the consent requirement, which annotations alone cannot convey.

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?

Two sentences, front-loaded with the effect and the no-catch-up rule, followed by the confirmation protocol. Nothing is padded and no sentence is redundant.

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 two-parameter mutation with no output schema, the description covers the effect, the time semantics, and the safety protocol. It does not say what the preview contains or how failures (e.g., a rule that is not paused) are surfaced, a minor remaining 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 coverage is 100% and the schema already documents both `id` (obtained from lister_messages_recurrents) and the `confirmer` preview/execute semantics. The description largely restates the confirm flag rather than adding syntax or format detail, so the baseline of 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 ("relance ... en pause") and resource ("message récurrent"), plus the key scope detail that the restart begins today. This implicitly separates it from suspendre/arrêter/modifier_message_recurrent, but it never names a sibling, so the differentiation must be inferred.

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 gives clear operating context: this applies only to a paused recurring message, and it prescribes a preview-then-confirm workflow with explicit human approval. It does not state what to do if the message is not paused or when to prefer modifier_message_recurrent instead, so the exclusions are missing.

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