zen_mute_tab

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

The description does not disclose behavioral traits such as whether the action toggles or sets the mute state, what happens when tab_id is null, or any side effects. With no annotations, the description carries full burden but fails to provide critical behavioral context.

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 concise, consisting of a single sentence, but it is too brief to be maximally helpful. It is appropriately front-loaded but sacrifices substance for brevity, earning a middle score.

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 absence of annotations, no output schema, and two parameters, the description is incomplete. It omits essential context like default behavior for null tab_id, the meaning of the mute state, and return values (e.g., success indication). This is insufficient for reliable agent invocation.

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%, so the description must add meaning to parameters. It does not explain that 'muted' likely sets the mute state (true=muted, false=unmuted) or that 'tab_id' defaults to the current tab when null. This lack of detail hinders correct parameter usage.

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 verb 'Mute or unmute' and the resource 'tab', making the purpose obvious. However, it does not specify what 'mute' means (e.g., audio, notifications), which could lead to ambiguity, especially compared to sibling tools that may affect tab state differently.

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 use this tool versus alternatives like zen_close_tab, zen_reload_tab, or zen_detach_tab. No conditions for appropriate use or exclusions are provided, leaving the agent to infer context from the tool name alone.

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