Server mute / unmute

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

No annotations exist, so the description must fully disclose behavior. It states the tool toggles mute and explains the boolean, but fails to describe side effects (e.g., what happens if the member is not in a voice channel, or if already muted/unmuted) or any other behavioral traits.

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?

The description is a single, concise sentence that conveys the essential purpose and basic usage. No unnecessary words or repetition; it earns its place.

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 simple toggle tool with no output schema, the description covers the core functionality. However, it lacks context on prerequisites, error handling, and differentiation from sibling tools. It is minimally complete but not thorough.

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?

The input schema provides 100% description coverage for all three parameters. The description adds only a small clarification ('Pass mute=false to unmute') which is already implied by the schema's 'true to mute, false to unmute.' Therefore, minimal added value beyond schema.

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 clearly states the action ('Toggle server-level mute') and the resource ('a member in a voice channel'), and specifies the boolean parameter usage. It is distinct from the sibling tool 'server_deafen' but does not explicitly differentiate itself; the verb 'toggle' and mention of voice channel help.

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?

No guidance is provided on when to use this tool versus alternatives like 'server_deafen' or other mute-related actions. There is no mention of prerequisites (e.g., member must be in a voice channel) or when not to use it.

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