delete_item

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

Annotations already declare destructiveHint=true, so the risky nature is covered structurally. The description adds one genuinely useful behavioral fact beyond the annotations: the operation is undoable, which softens the destructive profile. However it says nothing about scope of removal, whether the item's MIDI/audio content is preserved, or any confirmation requirement.

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?

A single front-loaded sentence with zero padding. It is efficient, though arguably too terse to be maximally useful for a destructive operation.

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 one-parameter delete tool with a destructiveHint annotation and a fully covered schema, the essentials are present, and the undo note helps. It still leaves open what exactly an "item" is in this DAW and whether deletion cascades (e.g. to associated notes or automation), which matters for a destructive tool with no output schema.

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 100% and item_id is fully documented in the schema (MIDI item id from create_midi_item/get_track_details, or "selected"). The description adds no parameter detail beyond the schema, so the baseline 3 applies.

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?

"Deletes an item" states a clear verb and resource, but "item" is generic and the definition does nothing to distinguish it from siblings like delete_track, delete_marker, delete_midi_notes, or delete_sound that share the same verb. An agent can infer it targets an arrangement item only by cross-referencing the schema's reference to create_midi_item.

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 when-to-use guidance, no mention of alternatives (e.g. edit_item vs split_item vs this), and no prerequisites. The parenthetical "(undoable)" is the only context offered and it is not framed as a usage rule.

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