timeline_delete_track

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

Annotations already declare destructiveHint=true, and the description's 'Delete' is consistent. However, beyond the bare action, the description does not disclose important behavioral traits such as the removal of all clips on the track or consecutive track indices shifting after deletion. This leaves the agent without side-effect awareness.

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, clear sentence with no redundant words. It is front-loaded and immediately states the purpose.

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 simple two-parameter tool with full schema coverage and a destructive annotation, the description is adequate but not comprehensive. It omits side effects like clip deletion and index reordering, which are relevant for a destructive operation. The existence of an output schema somewhat reduces the burden, but the lack of behavior disclosure keeps it at a minimal viable level.

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 already describes both parameters fully (track_type with allowed values, track_index as 1-based). The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate given 100% schema coverage.

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 a track from the current timeline' uses a specific verb ('Delete') and resource ('track') while clearly scoping to the 'current timeline'. This distinguishes it from sibling tools such as timeline_delete_clips, which deletes clips rather than tracks.

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 usage through the verb 'Delete' and mentions the 'current timeline' as context, but it does not provide explicit when-to-use versus alternative guidance or exclusions. No prerequisites like having a current timeline set are stated, and no alternative tools are referenced.

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