mcp_opendaw_invert_notes

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

No annotations are provided, so the description must fully disclose behavior. It describes the transformation and return count but does not mention whether the operation is destructive, reversible, or has side effects on the project state.

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 concise and well-structured, front-loading the purpose, then the formula, example, parameters, and return values without unnecessary words.

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 description covers parameters, behavior, and return values well, but omits error conditions, limitations, and prerequisite knowledge (e.g., MIDI note numbers). Since an output schema exists, the return description is not essential but adds 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?

With 0% schema description coverage, the description fully explains each parameter: unit_index, track_index, region_index (with special -1 meaning), and axis (default 60, pivot pitch) with usage tips, adding significant meaning beyond schema types.

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 inverts a melody around a pitch axis via mirror reflection, providing a formula and example that distinguish it from sibling tools like transpose or reverse.

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 explains how to use each parameter (unit, track, region, axis) and recommends using the first note's pitch for tonal inversion, but it does not explicitly guide when to choose inversion over alternatives or mention when not to use it.

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