delete_scene

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

With no annotations, the description carries full burden. It only states the action but omits critical behavioral traits: whether deletion is irreversible, what happens to contained clips, and any authorization requirements. The description is minimal and fails to disclose the destructive nature beyond the verb.

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 specifying the action and parameter, with no verbose or redundant text. Every word serves a purpose, making it easy for an agent to quickly parse.

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 destructive action with a single parameter, the description is somewhat incomplete: it does not mention output schema (though one exists), side effects on clips, or confirmatory feedback. However, given the simplicity and presence of an output schema, the description meets a minimum viable standard.

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. It adds the '0-based' specification for scene_index, which is helpful but does not provide range constraints, error behavior, or examples. The baseline for zero schema coverage is 4, but the description adds only minimal value, hence a 3.

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 tool name 'delete_scene' and description clearly state the verb 'delete' and resource 'scene', with the method 'by index'. This effectively distinguishes it from other scene-related sibling tools like create_scene, duplicate_scene, or fire_scene.

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 like duplicate_scene or fire_scene. There is no mention of prerequisites, such as ensuring the scene exists or handling errors, nor any context about its effect on clips or undoability.

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