piano_roll_delete_notes

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that notes are deleted based on a match; it does not explain scope (current pattern, selection, or whole project), exact matching semantics, irreversibility, or what happens to non-matching or malformed entries.

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 definition is a single front-loaded sentence with no filler. Every word contributes to the core operation and matching criterion, making it highly efficient even though more detail would be welcome elsewhere.

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 destructive parameterized tool with no annotations, no output schema, and an essentially undocumented notes array, this description is far from sufficient. An agent cannot reliably construct a valid call because the note object shape, match behavior, and deletion scope are not specified.

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 input schema gives the notes parameter no item structure or descriptions, and schema description coverage is 0%. The description provides the only hint that each note object should contain midi and time_bars, but it omits types, ranges, required keys, and whether additional properties are ignored during matching.

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 identifies the operation ('Delete notes') and the resource (piano roll notes), and adds a specific matching criterion ({midi, time_bars}). This is enough to distinguish it from broad operations like piano_roll_clear or add/duplicate tools, though it doesn't explicitly name alternatives.

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?

There is no guidance about when to use this tool versus alternatives such as piano_roll_clear or piano_roll_duplicate. The matching criterion implies targeted deletion, but the tool never states that partial deletion is its intended role or when the sibling clear-all operation should be preferred.

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