Remove Scene Item

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description 'Remove' aligns with these flags without contradiction. However, it adds no extra context about side effects (e.g., whether the underlying source is also deleted or if the action is reversible). Given the annotations cover the destructive nature, the description meets the baseline but does not enrich beyond it.

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, compact sentence that conveys the exact action without unnecessary verbosity. It is efficiently front-loaded and contains zero filler, earning a perfect score for conciseness.

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 destructive operation with full schema documentation and no output schema, the description is adequately complete. It informs the agent of the core action and pairs well with the annotations. Minor missing context (e.g., relationship to source) is not essential given the tool's simplicity, so only a slight deduction from perfect.

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%, so all four parameters (sceneName, sceneUuid, canvasUuid, sceneItemId) have descriptive comments in the schema. The description does not add any further parameter detail, which is acceptable given the high coverage and simple semantics. The baseline of 3 is appropriate.

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 'Remove a scene item from a scene' uses a clear verb+resource structure, precisely stating the action (remove) and the target (scene item within a scene). It distinguishes well from siblings like obs-remove-scene (removes whole scene) and obs-create-scene-item, making the tool's purpose unambiguous.

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 implies usage context (removing an item from a scene) but does not explicitly state when to prefer this over alternatives, such as obs-remove-scene for deleting an entire scene or obs-toggle-scene-item-enabled for toggling visibility. No exclusionary guidance is given, but the context is clean enough for a straightforward tool.

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