Mute or unmute a tab

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

The annotation readOnlyHint=false already signals a mutating operation, so the description's main added value is explaining that it toggles mute state and reports the resulting state. It does not disclose permissions, idempotency, behavior when the tab is already muted, or persistence, so it adds only moderate context beyond annotations.

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 three short sentences with the primary action front-loaded, followed by useful context and return-state information. Every sentence contributes without repetition or filler.

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 two-parameter tab mutation with 100% schema coverage and a readOnlyHint=false annotation, the description gives enough context: what it does, that it mirrors the context menu, and that it reports the resulting muted state. It is nearly complete, though it lacks details such as permission requirements or failure behavior.

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 100%, so both the 'muted' boolean and optional 'context' parameter are already documented. The description does not add syntax, default behavior for the context parameter, or edge-case semantics beyond what the schema provides, making the baseline score appropriate.

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 specific verb and resource ('Mute a tab ... or unmute it') and clearly identifies the operation as mirroring the tab context menu's mute item. It is readily distinguishable from sibling tab-management tools such as browser_pin_tab or browser_duplicate_tab.

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?

The description gives contextual usage ('so it stays silent in the background') and notes it mirrors the context-menu item, which implies when to use it. However, it does not explicitly state when to prefer this over alternatives or mention any exclusions or prerequisites, leaving selection guidance only implied.

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