write_bassline

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

No annotations are provided, so the description carries the full behavioral burden. 'Writes' implies mutation, but the description does not disclose whether existing notes are replaced, how the item is affected, what permissions are needed, or what the tool returns.

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?

A single front-loaded sentence with no wasted words. It is concise, though the brevity comes at the cost of detail captured under other dimensions.

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?

For a 10-parameter MIDI-writing tool with no output schema and no annotations, one sentence is far too thin. It omits the meaning of item_id, the effect of replace, how chord_length interacts with chords, and any side effects or return information.

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?

With 10 parameters and only 50% schema description coverage, the description should compensate but does not. It mentions chords and style implicitly, but adds no meaning beyond the schema for those or any of the other 8 parameters (seed, start, octave, velocity, chord_length, replace, key, item_id).

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?

States a specific verb and resource ('Writes a bassline') and the musical input ('follows the chords in a chosen style'). It is clear, but does not distinguish itself from siblings like write_melody or add_chord_progression.

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 when-to-use instruction, no conditions or alternatives. The phrase 'in a chosen style' implies context, but there is no guidance on when this tool is appropriate versus write_melody or add_chord_progression.

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