Delete track

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It reveals the destructive core action, 'Delete', but does not mention irreversibility, what happens to subsequent track indices, whether the operation can be undone, or what occurs on an invalid index.

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 with no padding. It conveys the tool's verb, resource, and the key parameter semantics inline while remaining highly scannable.

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 one-parameter tool, the description is mostly self-sufficient, but the absence of annotations and any information about side effects, error behavior, or return values leaves notable gaps. An agent can call it correctly for a valid index, but not fully understand the consequences of 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 describes the parameter 'index' only as an integer with minimum 0, but the description clarifies that this integer is a 0-based index into the track list, which is essential semantic context. This compensates for the 0% schema description coverage, even though edge-case behavior (e.g., invalid indices) is not covered.

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 states a specific verb ('delete') and resource ('the track... at the given 0-based index'). It distinguishes this destructive action from siblings like reaper_insert_track or reaper_set_track_volume, and there is no other delete tool among the siblings.

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 use case is implied: use it when you need to remove a track. However, the description gives no explicit when-to-use or when-not-to-use guidance and does not point to any alternative (e.g., undo or reaper_call) for zero-based destructive operations.

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