Delete scene

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

With no annotations provided, the description carries the full burden. It discloses that the action is permanent ('Permanently remove') and high-impact requiring confirmation. This is useful behavioral context, though it doesn't specify how confirmation is conveyed (e.g., the confirm parameter) or potential side effects like removal of associated sources.

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, consisting of two short sentences that immediately convey the core action and caution. No filler or redundant information; every word contributes value.

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 that an output schema exists, the description doesn't need to detail return values. It covers the essential aspects: permanent deletion and the need for confirmation. However, it could be more complete by explicitly stating that the confirm parameter must be set to true, and by noting any prerequisites or side effects. Overall, it is adequate for a simple destructive tool.

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 schema has 0% description coverage, so the description must compensate. It adds meaning to the confirm parameter through 'requires confirmation,' implying that confirmation must be explicitly given. The scene_name parameter is self-explanatory from its name and the description's reference to 'a scene,' but the description doesn't elaborate further on parameter formatting or requirements beyond that.

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 tool's function with a specific verb and resource: 'Permanently remove a scene.' This distinguishes it from sibling tools like create_scene, rename_scene, or duplicate_scene, and even from delete_source by specifying '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?

The description provides clear usage context by labeling the operation as 'High-impact: requires confirmation,' which signals that the agent should obtain user consent before invocation. It does not explicitly name when not to use or mention alternatives, but for a straightforward destructive operation, this guidance is sufficient.

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