midi_delete_note

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

Annotations are absent, so the description must disclose behavior. It only says 'Delete a note' without describing what happens if the note doesn't exist, reversibility, side effects, or any constraints. This is insufficient for a mutation tool.

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 very short (one sentence plus parameter list), which is concise. However, the minimal content sacrifices clarity. It is front-loaded with the purpose but lacks necessary details.

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 simplicity of the operation, the description is partially complete but lacks behavioral context (e.g., return value, error handling). With no output schema, the user is left uninformed about the result of the deletion.

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?

The schema has 0% description coverage, and the description only lists parameter names without adding meaning. For example, 'item_index' and 'note_index' are not explained (e.g., how to obtain them, valid ranges). The description adds no value beyond the schema structure.

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 'Delete a note' clearly states the verb (delete) and resource (a note). It is straightforward, but it does not distinguish from sibling tools like midi_delete_all_notes or midi_delete_cc, leaving potential ambiguity.

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 usage guidance is provided. There is no information on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description merely states the action.

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