obs-remove-scene

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies destruction via the word "Remove." It never mentions that deletion is irreversible, what happens to the scene's items and sources, or that the confirm flag is gated by the OBS_PROTECT_DESTRUCTIVE environment setting.

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?

It is a single short sentence with zero filler and the action front-loaded. Brevity here is efficient rather than padded, though it is arguably too terse for a destructive operation.

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 mutation with no annotations and no output schema, the description should at minimum cover irreversibility and the confirmation requirement. As written, the agent must infer all risk and side-effect information from the schema alone.

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 100%, with both sceneName and confirm documented in the schema itself, so the baseline of 3 applies. The description adds no extra meaning about the required scene name or the conditional confirmation behavior.

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 names a specific verb and resource ("Remove a scene") and scopes it to OBS, so the agent knows exactly what object is affected. It does not, however, distinguish this from close siblings such as obs-remove-scene-item or obs-remove-profile, which a five would require.

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?

There is no guidance on when to use this versus obs-create-scene, obs-set-current-scene, or obs-remove-scene-item, and no mention of preconditions. Nothing tells the agent whether the scene must be inactive, whether the current scene can be removed, or what to do if the name is wrong.

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