adjust_current_sound

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

No annotations are present, so the description carries the full burden. It discloses that the tool writes to the currently loaded preset ('Space Dust'), that the plugin picks up changes automatically, and that it requires a preset to be selected. This covers the key behavioral traits, though it doesn't mention error cases or undo behavior.

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 and front-loaded: it states the core action first, gives quick examples, then mentions the side-effect and prerequisite. Every sentence earns its place, with no 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?

It covers use-case, side-effect, immediacy, and prerequisite. An output schema exists, so return values are delegated. The only notable omission is parameter structure, already penalized separately, making the overall context fairly complete.

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% and the description never explains the structure of the `changes` object. The examples ('make this darker') imply intent, but an agent cannot determine what keys or values to put in the `changes` map, leaving a critical gap for correct invocation.

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 opens with a specific verb and resource: 'Change the sound the user is playing right now.' It clearly distinguishes this from adjusting a preset by name via examples like 'rather than a preset by name,' which differentiates it from sibling adjust_preset.

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?

It explicitly tells when to use this tool: for sonic descriptions like 'make this darker' or 'more bite' rather than preset names. It also states the prerequisite that a preset must be selected and instructs asking the user to save unsaved sounds first, providing clear context and exclusions.

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