imgui_delete_scene

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether deletion is permanent, whether it affects the currently active scene, whether other scenes are impacted, or what happens on success/failure. For a destructive operation with zero annotation coverage, this is a significant gap.

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 a single concise sentence with zero waste. It is short and to the point, though it lacks the supplementary behavioral context that would make it more helpful.

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?

This is a destructive mutation tool with no annotations and no output schema. It has 1 parameter at 100% coverage, but for a delete operation the description should convey permanence, consequences, and any prerequisites. It does none of these, making it incomplete for a 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?

Schema coverage is 100% with one parameter (name) described as 'Scene name to delete'. The description adds no semantic detail beyond the schema. Baseline 3 is appropriate since the schema fully documents the parameter.

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 "Delete a scene by name" clearly states the verb (delete) and resource (scene). However, it doesn't distinguish from sibling tools like imgui_delete_snapshot, and given there are scene-management siblings (imgui_create_scene, imgui_switch_scene, imgui_list_scenes), the purpose is clear but contextual differentiation is absent.

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, whether scenes must exist first, whether errors occur for non-existent scenes, or any relationship to switching/creating scenes. No when-to-use or when-not-to-use guidance is provided.

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