delete_item

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

With no annotations, the description carries the full behavioral burden. 'Delete' implies a mutation, but nothing is said about irreversibility, undo availability, error behavior when indices are out of range, or whether the item is removed from disk or just the project. For a destructive operation with zero annotation coverage this is a real gap.

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 short sentence is front-loaded and wastes no words, but it is under-specified rather than genuinely concise. There is no structure beyond the bare statement of action.

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?

A destructive, two-parameter tool with no annotations, no output schema, and no parameter documentation leaves the agent without enough to call it safely. At minimum, index semantics and undo/reversibility should be stated.

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% for both required parameters. The description's phrase 'media item' faintly hints that item_index addresses an item, but it never explains track_index vs item_index, indexing base, or whether item_index is scoped to the track. It does not compensate for the coverage gap.

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 states a specific verb and resource ('Delete a media item'), so the agent knows it removes an item. However, it gives no differentiation from close siblings like delete_selected_items, delete_take, or delete_midi_note, which also remove content. Clear but undifferentiated, matching the 4 criteria.

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 use this versus delete_selected_items or delete_take, and no prerequisites such as selection state or whether the item must be unselected first. The agent must infer usage entirely.

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