track_delete

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action without revealing side effects (e.g., whether deleting a track removes its clips, affects timeline structure, or if confirmation is required). No mention of destructiveness or irreversibility.

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 sentence, but it is underspecified rather than concise. It lacks critical information that could be added without bloat, such as parameter details or usage context. The brevity sacrifices completeness.

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 empty annotations, no output schema, and minimal description, the tool is poorly documented for an AI agent. The description fails to cover basic aspects like return values, error conditions, or how the index relates to timeline tracks. It is insufficient for reliable selection and invocation.

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%, and the description adds no meaning beyond the parameter names and types. It does not explain what 'track_type' values are valid (e.g., 'audio', 'video') or the range/scope of 'track_index'. This leaves the agent guessing about correct usage.

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 'Delete a track by 1-based index.' It identifies the action (delete), the resource (track), and a key constraint (1-based index). This effectively distinguishes it from sibling tools like track_add or track_rename.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like ensuring the track exists or that the index is valid. There is no 'when not to use' or reference to other track operations.

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