mute

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

The description states 'Mute system output', implying a mutating action, which aligns with the readOnlyHint=false annotation. However, it does not disclose side effects (e.g., behavior when already muted, impact on volume level). The annotation covers the write nature, but the description provides no additional transparency.

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 sentence that directly states the tool's purpose with no filler. It is appropriately concise for a parameterless tool.

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?

Given the simplicity (no parameters, no output schema), the description covers the essential functionality. It could mention the absence of return values or confirm success, but it is largely complete for its context.

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?

There are no parameters, so the description does not need to add meaning. The schema coverage is 100% (empty properties). Baseline for zero parameters is 4, and the description is adequate.

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 'Mute system output' uses a specific verb and resource, clearly indicating the action. It distinguishes from sibling tools like 'unmute' and 'set_volume' by directly naming the opposite action.

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 such as 'set_volume' or 'toggle_dark_mode'. Without explicit context, the agent may not know preferred use cases.

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