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

Annotations already declare this is a non-read-only, non-destructive mutation, so the description's job is narrower. It usefully adds that muting is scoped to 'yourself' (per-user, not global), but says nothing about idempotency, what happens when already muted, or required conversation membership.

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?

A single short, front-loaded sentence with no padding. The parenthetical code adds no actionable information, which keeps it from a 5.

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?

An output schema exists so return values need no explanation, but with zero schema coverage on two parameters and no usage context, the definition leaves the required conv_key largely unexplained. For a mutation tool, more behavioral framing is needed.

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 0% for both parameters. The description implies the `muted` boolean semantics through 'mute or unmute', but `conv_key` — the only required parameter — has no explanation of format or how to obtain it from list_conversations.

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 clear verb pair (mute/unmute) and resource (conversation), so the agent knows exactly what operation happens. It does not distinguish itself from nearby siblings such as mark_read or list_conversations, so it falls short of a 5.

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 mute versus unmute, prerequisites, or which sibling handles adjacent notification concerns. The '(M-02)' tag is an internal reference an agent cannot act on.

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