delete_timeline

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

No annotations are present, so the description must fully disclose behavioral traits. It only states 'Delete a timeline by name' without explaining whether deletion is permanent, if clips inside are also deleted, if the operation is reversible, or if any permissions are required. This is insufficient for an agent to understand implications.

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 extremely concise: one sentence plus an Args line, no wasted words. It front-loads the purpose and clearly lays out the parameter. Every sentence earns its place given the simplicity of the tool.

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 has one required parameter and no complex behavior, the description covers the core action. However, it omits information about return value (though an output schema is indicated but not shown) and any side effects on related objects (e.g., clips, markers). For a deletion tool, more context about irreversibility 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 description repeats the parameter name and adds a minimal label ('Name of the timeline to delete'), which adds almost no meaning beyond the schema. The schema lacks a description for 'name', so the description offers marginal help but no constraints, format, or examples. For a single required parameter, the semantics are barely adequate.

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'), and the parameter 'name' specifies which timeline. It distinguishes from sibling tools that operate on timeline markers, tracks, clips, etc., as it specifically targets the timeline itself.

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. There is no mention of prerequisites (e.g., timeline must exist or not be locked), side effects, or conditions under which deletion fails. Sibling tools like delete_clips or delete_track operate on different entities but no comparative guidance is given.

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