delete_track

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is known. The description adds two things annotations cannot convey: the deletion cascades to everything on the track, and the operation is reversible via undo. It stops short of describing permissions or return content, but the meaningful additions are there.

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 sentence with the core action front-loaded, cascade scope second, and reversibility as a compact parenthetical. Nothing wasted, nothing buried.

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?

An output schema exists, so return values are covered, and annotations cover the destructive profile. But for a four-parameter mutation with zero schema documentation, the description should clarify how the track is identified and how project/sequence scoping resolves; that gap keeps it at minimum viable.

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% across four parameters, and the description compensates for none of it. An agent gets no help on whether 'track' is an index or a name (the schema allows both integer and string), or what 'project', 'sequence', and 'kind' default to when omitted.

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?

States a specific verb and resource ('Remove a track') plus cascade scope ('and everything on it'), so the agent knows exactly what is affected. It doesn't distinguish itself from the sibling delete_track_items or from update_track, but the core action is unambiguous.

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 indication of when to choose this over delete_track_items, or whether prerequisites exist (empty track, active sequence). The only usage-adjacent signal is the parenthetical '(undoable)', which is informational rather than routing guidance.

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