set_channel_eq_on

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

With no annotations, description must carry full burden. It only says 'enable or disable' but does not disclose reversibility, side effects, or whether existing EQ settings are preserved.

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?

Single sentence, front-loaded, no unnecessary words.

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 annotations and 2 required params, description is minimal. Doesn't explain output or constraints. Sibling tools have richer descriptions.

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 coverage is 0%, so description should compensate. It gives no meaning beyond parameter names. 'channel' could be string or integer but no format hint; 'enabled' is obvious.

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?

Description clearly states the action (enable/disable), resource (EQ), and target (channel). It is specific and distinguishes from sibling tool set_channel_eq which likely sets EQ parameters.

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 guidelines on when to use this tool vs alternatives like set_channel_eq. No prerequisites or context for use provided.

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