ableton_delete_return_track

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It merely states the deletion action without detailing permanence, side effects (e.g., removing sends), or any undo capability. This is insufficient for a mutation operation.

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 sentence with no extraneous words. It is efficiently short but sacrifices necessary detail, making it slightly under-informative for its conciseness.

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 tool has only one parameter and no output schema, the description is minimally adequate. However, it fails to explain the parameter's role or the deletion's impact, and lacks guidance on using sibling tools like ableton_list_returns to determine the correct index.

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%, meaning the description should supplement the schema. However, the description does not mention the required 'returnIndex' parameter or clarify its meaning (e.g., 0-based index). The schema provides technical constraints but no semantic context.

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 an Ableton return track' clearly states the action (delete) and the target resource (Ableton return track), distinguishing it from sibling tools like ableton_create_return_track and ableton_modify_return.

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 description implies when to use (when wanting to delete a return track) but provides no explicit guidance on prerequisites, such as whether the track can be deleted if it's the last return track or if it's currently in use. No exclusions or alternatives are mentioned.

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