mcp_opendaw_set_piano_note_labels

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

The description discloses the return value (old and new values) and the toggle nature, but with no annotations, it misses potential side effects or prerequisites. For a simple toggle, it is adequate but not rich.

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?

Three concise sentences: purpose, parameter explanation, and return description. No redundancy, well front-loaded.

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 simple toggle with one parameter and output schema present, the description is adequate but could mention the scope (e.g., selected track). Overall, meets minimum viability.

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?

Given 0% schema description coverage, the description adds meaningful explanation of the boolean parameter 'show', specifying its effect. This compensates well for the schema's lack of text.

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 toggles note labels in the piano roll, specifying the resource (note labels) and action. However, it does not explicitly distinguish from sibling tools like set_piano_keyboard, but the purpose is specific enough.

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 show vs hide labels or alternatives. The description lacks context for when to use this tool over others.

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