delete_track

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

No annotations are provided, so the description carries the full behavioral burden. It never states that this is destructive/irreversible, whether the action is undoable, what happens to the track's items, FX, and sends, or whether subsequent track indices shift. For a destructive mutation tool with zero annotation coverage, this is a substantial 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?

Only two short lines, with the core action front-loaded before the argument note. There is no filler, though the 'Args:' block style is terse rather than maximally informative.

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 single-parameter destructive tool with no annotations and no output schema, the description covers the parameter and one important restriction (master track). It omits return/confirmation behavior and side effects on routed sends, items, or FX, leaving an agent without enough to predict consequences.

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% (the schema only says 'integer'), so the description must compensate, and it does: it specifies the index is 0-based and that the master track (-1) is an invalid target. That adds real meaning beyond the bare schema, though it doesn't note whether indices shift after deletion.

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 track'), which is unambiguous against siblings like delete_take, delete_send, or delete_item. It does not explicitly contrast itself with those siblings, but the resource name is distinct enough that an agent can select it correctly.

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 explicit when-to-use guidance or named alternative, but the description does impose a meaningful scoping constraint: the target cannot be the master track (-1). That is a partial 'when-not' rule, though it stops short of saying when this tool should be preferred over other track-management operations.

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