delete_scene

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds a useful non-obvious behavior: 'Higher scene indices shift down.' This informs the agent about side effects beyond the delete operation, though it does not mention error handling or reversibility.

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—two short sentences—with no filler. Both sentences add value: the first states the action, the second clarifies the reindexing behavior.

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?

For a simple delete operation, the description is minimally adequate. It specifies the core behavior and one side effect, but lacks context about edge cases (e.g., invalid index) and does not mention that the operation is destructive, though this is implied by the verb 'delete.' The presence of an output schema covers return values.

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%, so the description must compensate for the lack of parameter details. It does not elaborate on 'scene_index' beyond the schema's type and requirement, leaving ambiguity about index base (0-based vs 1-based) or valid range.

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 a scene') with a specific verb and resource. It also distinguishes this tool from sibling tools like delete_clip and delete_track by clearly indicating it operates on scenes.

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 usage is implied: if you want to delete a scene, use this tool. However, it provides no explicit context about when to use it versus alternatives, nor any prerequisites or exclusions.

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