delete_track

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

With no annotations, the description must disclose behavioral traits but only states a destructive action. It does not mention whether the deletion is permanent, reversible, or what happens on error (e.g., invalid index or track type). This lack of transparency may lead to incorrect usage.

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 concise with one sentence stating the purpose, followed by a clear list of parameter descriptions. No extraneous information, and it is front-loaded with the primary action.

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's simplicity (two parameters, straightforward action), the description provides the essential purpose and parameter meanings. However, it lacks context about expected behavior on success/failure, error handling, or side effects. Since no annotations are present, more completeness would be beneficial for an agent to use the tool safely.

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?

Although the input schema has 0% description coverage, the description adds meaningful semantics: it specifies that 'track_type' is one of 'video', 'audio', or 'subtitle', and that 'index' is 1-based. This clarifies the schema constraints beyond the raw type definitions. However, it could further specify allowed values or boundaries.

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 explicitly states 'Delete a track from the current timeline,' clearly indicating the action (delete) and the resource (track on timeline). It distinguishes from siblings like 'add_track' or 'delete_timeline' which operate on different resources or have different verbs.

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 guidance is provided on when to use this tool versus alternatives, such as deleting clips or other track operations. There is no mention of prerequisites (e.g., timeline must be active) or conditions for use, leaving the agent to infer context.

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