delete_timeline

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

With no annotations, the description carries full behavioral disclosure burden, but it only states 'Delete a timeline by name.' It fails to mention that deletion is likely irreversible, whether it affects clips or tracks inside the timeline, or if any confirmation is required. The minimal information does not adequately inform the agent of the tool's consequences.

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, front-loaded sentence with no wasted words, making it concise. However, it is overly terse and sacrifices necessary detail for brevity. For a tool with only one parameter, this might be acceptable, but the lack of behavioral or usage context reduces its value.

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 (one parameter, no output schema), the description might seem complete, but it omits critical information for a deletion operation. It does not mention irreversibility, confirmation steps, or what happens to related data (e.g., clips). Compared to sibling tools, more context (e.g., 'irreversibly deletes') would improve completeness.

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 has 0% description coverage, so the description must compensate. However, it only restates the parameter name by saying 'by name' without adding constraints (e.g., case sensitivity, uniqueness, format). The parameter is already self-explanatory from its name, but the description offers no additional semantics beyond the schema.

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 the action (delete) and the resource (timeline) with the identification method (by name). This is specific enough to understand the tool's primary purpose, though it does not differentiate from sibling deletion tools like delete_clips or delete_track.

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 delete_clips or delete_track. There is also no mention of prerequisites (e.g., timeline existence, user permissions) or side effects, leaving the agent without context for proper invocation.

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