generate_bassline

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention whether the tool overwrites existing clip content, what happens if the track is not a bass track, or any rate limits or side effects. The suggestion that track_index should be a bass track is informal and lacks clarity.

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: a single sentence stating purpose followed by a bulleted list of parameters. Each parameter explanation is brief but informative. There is no unnecessary repetition or fluff, though the format could be slightly more streamlined.

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 all parameters and their roles, but it lacks information about return values or side effects. Given the tool's generative nature and no output schema, more details about what the bassline pattern looks like or if it returns any confirmation 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%, so the description's parameter explanations are essential. It adds meaning beyond schema titles: e.g., 'root: Root note MIDI number (36 = C1, common bass range)', 'scale_type: Scale to use (minor, major, dorian, pentatonic_minor, blues)', 'length: Pattern length in beats'. This adds significant value.

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 tool's purpose: 'Generate a bassline pattern and add it to a clip.' It uses a specific verb ('generate') and resource ('bassline pattern'), and the action ('add to a clip') is unambiguous. This distinguishes it from sibling tools like generate_drum_pattern and add_notes_to_clip.

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 guidance is provided on when to use this tool versus alternatives. For example, it does not clarify when to prefer this over add_notes_to_clip or generate_drum_pattern. The description simply lists parameters without contextual usage advice.

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