compose_rainstorm

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

The description discloses the generated audio content (rain bed, wind layer, thunder rumbles) and processing hints (lowpass, EQ, low gain), plus the 60 BPM grid. However, it does not explicitly state whether the tool writes a file, overwrites an existing file, or returns a status/result, and with no annotations the description carries the full transparency burden.

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 a single compact sentence with a clear colon-separated list of sonic elements. Every phrase adds useful information without redundancy 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?

The description gives a good high-level sense of the tool and its output type, but it omits important context such as file-writing behavior, parameter semantics, and any return value. Since there is no output schema or annotations, this is not fully complete for an agent to invoke confidently.

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 only 33% (only 'seed' has a description), and the description does not compensate by clarifying 'out_path' or 'length_seconds'. The 60 BPM note and rain/wind/thunder details give sonic context but do not explain the meaning or interaction of the parameters.

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 names a specific verb ('Generate'), a concrete output resource ('.tracktionedit'), and a distinct genre/sound ('rainstorm ambient'). It is clearly differentiated from the many sibling composition tools that target lofi, synthwave, jazz, etc.

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 clear context that this is for rainstorm ambient sound generation, including the 'No music' note, which implicitly steers an agent away from the melodic composer siblings. It does not explicitly name alternatives or state when not to use it, so it stops just short of a 5.

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