add_genre_groove

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

No annotations are provided, so the description carries the full burden. It never discloses that this is a mutation that writes MIDI notes onto a track, whether it overwrites existing content (the 'replace' param exists but is unexplained), permission requirements, or what happens on repeat. Behavioral context is largely absent.

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 compact sentence, front-loaded with the verb and resource. Nothing is wasted, though its brevity comes at the cost of the missing usage and parameter detail noted elsewhere.

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 6-parameter mutation tool with no annotations, no output schema, and only 33% schema coverage, the description is too thin. It omits what replace, humanize, start, and repeats do, and does not explain the return or side effects, leaving an agent with real gaps before invocation.

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 only 33% (item_id and repeats documented in the schema). The description mentions no parameters at all, leaving genre, start, replace, and humanize undocumented in both the description and the schema. It adds no meaning beyond the structured fields.

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 ('Programs') and resource ('a genre's signature drum groove') and adds the mechanism ('from its profile') and the swing detail. It is clearly distinguishable from generic siblings like add_midi_notes, though it does not explicitly contrast with add_drum_pattern, which is the nearest alternative.

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 or when-not guidance. The description does not tell the agent how this differs from add_drum_pattern or add_midi_notes, nor that a genre profile (get_genre_profile/list_genres) is the source it depends on. Usage is only weakly implied by the phrase 'genre's signature groove'.

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