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

Annotations declare a non-read-only, destructive write but say nothing about execution mechanics; the description fills that gap with the concrete two-step flow (PROPOSED, status='confirmation_required', action_id, plan_token, then confirm_action) and the renderer for status='confirmation_required'. It also defuses the destructiveHint label by explaining that nothing is deleted and the action is reversible via muted=false.

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, front-loaded with the action and its inverse, followed by the behavioral clarification and the confirmation caveat. No redundant restatement of the title or annotations.

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 what changes, what does not, how to reverse it, and the exact confirmation handshake including the returned status fields. Nothing an agent needs in order to call it safely 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 coverage is 50%; the muted parameter is documented in the schema only as 'Default true', while the description supplies its actual semantic meaning (false = unmute). thread_id is left implicit, but its intent is unambiguous.

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 and resource (mute a conversation/thread) and immediately covers the inverse operation with 'unmute it with muted=false'. The clarification that messages keep arriving and stay readable distinguishes it from deletion or blocking siblings without needing to name them.

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 explains the two usage modes (mute by default, unmute via muted=false) and the required confirmation workflow before any write. It stops short of explicitly contrasting with plausible alternatives like a block-sender or snooze tool, so routing between similar tools is only partly supported.

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