set_energy

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

The description discloses that auto-play occurs after applying the energy level, which is a behavioral trait beyond the schema. With no annotations, this adds important context, though it could mention additional effects like resetting playback position.

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?

Two concise sentences, front-loaded with the core action and scale, then detailed mapping and auto-play side effect. No redundant words, effectively structured.

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 one-parameter tool with no output schema, the description adequately covers purpose, parameter meaning, and a behavioral note (auto-play). It could mention if it replaces or modifies existing energy, but it's sufficient for selection and 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 coverage is 100%, but the description adds semantic value by mapping numerical levels to qualitative terms (e.g., 'minimal/ambient', 'sparse'). This enriches the numeric range beyond the schema's basic description.

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 'adjust' and resource 'overall energy level of the current pattern', providing a specific and actionable purpose. It distinguishes itself from siblings like 'set_tempo' or 'shift_mood' by focusing on energy level.

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 implicitly indicates context (adjusting energy level of pattern), but does not explicitly state when to use this tool versus alternatives or any exclusions. It lacks guidance on prerequisites or scenarios.

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