track_remove

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Remove' implies deletion, the description lacks details on destructiveness, undoability, or whether underlying audio files are affected. It mentions track(s) can be plural, indicating batch capability.

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?

Two sentences with zero waste: first states the operation, second states the prerequisite. Perfectly front-loaded and appropriately sized for the tool's complexity.

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 simple schema and lack of output schema, the description adequately covers the essential usage pattern (selection prerequisite). It appropriately references the sibling tool track_select. Minor gap in not describing the mutation's permanence or return confirmation.

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 has zero parameters, establishing a baseline of 4. The description adds value by explaining the implicit input mechanism—the 'currently selected' state—referencing track_select as the mechanism to populate this state.

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 the action ('Remove') and resource ('currently selected track(s)'), distinguishing it from clip-level operations like edit_delete. It effectively signals this is a track management operation rather than an audio content edit.

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?

Explicitly states the prerequisite workflow ('Select tracks first with track_select'), guiding the agent on the correct sequence of operations. However, it doesn't explicitly contrast with alternatives like track_mute or warn against using it when tracks shouldn't be deleted.

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