generate_bassline

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

No annotations are provided, so the description must carry the full burden of behavioral transparency. It states that a bassline is 'added' to a clip, but does not disclose whether existing notes are overwritten, whether the clip must already exist, or any side effects. Given this is a mutating generative tool, this lack of detail is a notable gap.

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 compact and front-loaded with a clear purpose sentence, followed by a succinct parameter list. Every sentence adds value, and the structure makes it easy to scan for key arguments.

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 covers the input parameters well but omits behavioral outcomes (e.g., return value, clip content replacement) and does not mention output schema (none exists). Given the lack of annotations and output schema, more context about what happens after generation would improve completeness.

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%, yet the description fully compensates by explaining each parameter with meaningful context: root is a MIDI number with example, scale_type lists allowed values, length is in beats, and track_index should point to a bass track. This goes well beyond the bare schema properties.

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 states a specific action: 'Generate a bassline pattern and add it to a clip.' This clearly distinguishes it from the sibling tool 'generate_drum_pattern' by focusing on bassline creation rather than drums. The verb and resource are both explicit.

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 implies use for bassline generation but does not explicitly compare it to alternatives like generate_drum_pattern or state when not to use it. The parameter note that track_index 'should be a bass track' offers some contextual guidance, but there is no clear when-to-use vs. alternative.

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