gen_emit_bassline

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

No annotations are provided, so the description carries full burden. It only says 'Create a bassline', implying mutation, but gives no details on side effects (e.g., whether it clears existing notes, modifies channel data, or requires specific setup). This is insufficient for safe invocation.

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 sentence with no waste, but it lacks important information. It states the purpose concisely, which earns its place, but the scope is insufficient for a tool with 8 parameters.

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?

With 8 parameters, no output schema, and no annotations, the description is far too sparse. An agent cannot determine how to use this tool correctly or what to expect without much inference. The description fails to provide adequate context.

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?

The description does not add any meaning to the parameters beyond the schema. Schema description coverage is 0%, and the description only vaguely references 'various styles' and 'chord progression root', which hint at progression and pattern_style but do not clarify usage, defaults, or constraints.

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 the action ('Create a bassline') and the resource ('bassline that follows a chord progression root'), which is clear and specific. It distinguishes from sibling tools like gen_emit_melody or gen_emit_arpeggio by specifying bassline and referencing chord progression root.

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 on when to use this tool versus alternatives like gen_emit_arpeggio or gen_emit_melody. No context about prerequisites or exclusions is provided.

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