ReaMCP

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

With no annotations provided, the description carries the full burden. It discloses the destructive 'delete' operation and the 0-based indexing scheme, but omits safety context (e.g., whether changes are reversible via the 'undo' sibling tool), error behavior for invalid indices, or concurrency implications.

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 a single, front-loaded sentence of 12 words. Every word earns its place: the action, the target, the container (MIDI item), and the key addressing constraint (0-based index) are all efficiently packed 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?

Given the tool has an output schema (reducing the need to describe return values) but 0% input schema coverage and no annotations, the description is minimally adequate. It identifies the resource clearly but should have cross-referenced get_midi_notes for obtaining the index and clarified the addressing scheme for all three parameters given the complexity of nested DAW object addressing.

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% (only titles provided). The description compensates partially by specifying that note_index is '0-based', which is critical semantic information not in the schema. However, it fails to document track_index or item_index (whether they are also 0-based, their relationship to the project structure, etc.).

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 provides a specific verb ('Delete') and resource ('MIDI note') and clarifies the addressing method ('by its 0-based note index'). However, it does not explicitly distinguish from siblings like set_midi_note (update vs delete) or indicate the relationship to get_midi_notes (typically needed first to obtain the index).

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 mentions the '0-based note index' requirement but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention that one must typically call get_midi_notes first to obtain the note_index. There are no prerequisites, warnings, or workflow hints.

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