mcp_opendaw_analyze_harmonic_rhythm

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

Annotations declare readOnlyHint=true, and the description discloses several behavioral traits beyond that: it identifies chords using the same logic as identify_chords, returns specific analysis outputs (chord change positions, durations, rate, density, stable/active sections, total events), and notes the data source is MIDI notes. This adds substantial context about what the tool does with input and what it produces.

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 appropriately structured with a clear summary, bullet-point output list, comparison to related tools, usage suggestions, parameter definitions, and a return value statement. Each section earns its place without redundancy.

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 tool has an output schema (though its content is not shown in the provided context), so return values may already be documented there. The description covers usage context, input semantics, and output types at a level appropriate for the tool's complexity. It could be improved by explaining why region_index defaults to -1 meaning 'first' rather than all regions, but overall it is complete for selection and 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 0%, but the description includes a brief parameter list with defaults and meanings (unit_index, track_index, region_index with -1 = first and -2 = all regions, group_tolerance as beats of tolerance, min_notes as minimum notes). Though concise, it provides essential semantics for all five parameters.

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: analyze harmonic rhythm (how fast chords change and where), listing the specific outputs. It distinguishes itself from sibling identify_chords by explicitly focusing on the temporal pattern of harmony.

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?

The description explicitly says when to use this tool vs alternatives, naming identify_chords as complementary and listing three specific sibling tools to use with it: analyze_song_structure, reharmonize_progression, and create_arrangement_variation.

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