delete_sequence

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

With no annotations, the description carries full behavioral burden, yet it does not say whether deletion is permanent, whether undo can restore it (an undo tool exists among siblings), whether the source media is touched, or what happens if the sequence is currently active. It signals destructiveness only through the verb 'Delete'.

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?

A single short sentence with no filler and the action front-loaded. It is efficient, though brevity here borders on under-specification rather than tight writing.

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?

The tool is simple (one required ID, no output schema), so the bar is low, but for a destructive operation with zero annotations the description should say at least whether the action is reversible or how to obtain the sequenceId. As written it is adequate but leaves out the details an agent would want before deleting.

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?

There is a single required parameter with 100% schema description coverage ('The sequence ID to delete'), so the schema fully documents it. The description adds no format hints, ID-source hints (e.g. from get_sequences), or validation notes, making 3 the correct baseline.

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 names a specific verb (Delete) and resource (a sequence), scoped to the project, so the agent can tell it is not a clip or project-item deletion. It does not explicitly distinguish itself from neighbors like remove_clip, ripple_delete, or delete_project_items, but the resource noun does most of that work.

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?

There is no guidance on when to use this versus delete_project_items, ripple_delete, or remove_clip, and no stated prerequisites (e.g. whether the sequence must be closed or inactive). The agent must infer usage entirely from the name.

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