delete_scene

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that a scene is deleted, but does not mention consequences such as whether clips in the scene are also removed, whether the operation is undoable, or what happens if the scene index is invalid. This is insufficient for a destructive operation.

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 with no wasted words. The two-sentence structure plus parameter list is easy to scan. However, it omits critical behavioral context, so while efficient, it sacrifices completeness for brevity.

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 tool, the description reveals the action but lacks essential context for safe invocation. It does not explain side effects, error conditions, or prerequisites. Given the absence of an output schema and annotations, this description is inadequate for a destructive operation.

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 says 'scene_index: The index of the scene to delete,' which merely restates the schema's 'Scene Index' title and confirms it's an index, but adds no further semantics like zero-based vs one-based indexing or how to discover the correct index. Minimal value beyond structured fields.

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 and resource: 'Delete a scene.' This is a specific verb+resource combination that distinguishes it from sibling tools like delete_clip, delete_track, and delete_device. No ambiguity exists for the tool's core function.

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 description provides no guidance on when to use this tool versus alternatives like stop_scene, fire_scene, or select_scene. There are no exclusions, prerequisites, or context about scene deletion behavior. The agent must infer usage from the tool name alone.

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