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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real context beyond that by naming the two resulting states (paused vs draft), which is a mutation-relevant distinction. However it omits what happens when status is omitted, whether pausing is reversible, and any permission requirements.

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 sentence with the effect front-loaded and no filler. It is efficient, though arguably over-compressed for a mutation tool whose routing and default behavior remain unexplained.

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 small two-parameter mutation with no output schema, the definition is minimally adequate. It still leaves two operational questions unanswered: the default status when the optional parameter is omitted, and how this differs from update/delete/publish siblings.

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 50%: messageId is documented in the schema ('Proactive message id from list_proactive_messages') but the status enum has no schema description. The description partially compensates by naming 'paused' and 'draft', the two enum values, but it does not explain the default when status is omitted, which is the key ambiguity for this optional 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 states a concrete effect ('Stops showing a live message') and maps the two possible end states, paused and draft, to the tool's outcome. It is clear what the tool does, but it never distinguishes itself from close siblings such as update_proactive_message, publish_proactive_message, or delete_proactive_message, so an agent must infer the boundary.

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 when-to-use guidance: nothing says whether this is the right call versus update_proactive_message or delete_proactive_message, nor whether the message must already be live or published. Only the bare effect is described, leaving routing between siblings to inference.

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