gen_emit_melody

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

No annotations provided. Description mentions 'random melody' and scale constraint but does not disclose that it overwrites existing notes (clear_first parameter) or any side effects. For a mutation tool, this is insufficient.

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?

Single sentence, 16 words, concise but missing structure. Does not front-load critical info like 'channel' requirement. Every word is earned but not enough coverage.

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 9 parameters, no output schema, and no parameter descriptions, the description is severely incomplete. Does not explain behavior of 'pattern', 'seed', or 'clear_first'. No mention of return value.

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%. Description adds no parameter details beyond names and types. Does not explain 'seed', 'pattern', 'clear_first', or how 'root' and 'scale' combine to define the scale.

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 verb 'generate', resource 'melody', and output 'write it to the piano roll'. It specifies 'stays within the given scale' which differentiates from other gen_emit tools like bassline or arpeggio.

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 vs alternatives like gen_emit_bassline. No prerequisites mentioned (e.g., channel must exist). No exclusions or when-not-to-use.

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