remove_scene

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Delete a scene') without revealing irreversibility, side effects on scene items, or any required permissions. This is a significant gap for a destructive tool.

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 appropriately minimal for a tool with one parameter. It uses a clear structure: a one-line summary followed by an Args section. No unnecessary words or redundancy.

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?

The description is incomplete for a destructive operation. It lacks warnings about permanence, impact on scene items, or any usage context. While the parameter is documented, the absence of behavioral notes makes it under-specified for safe and correct invocation.

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 description adds meaning to the parameter beyond the schema, which only provides type and title. It specifies that scene_name is the 'Name of the scene to remove', clarifying its purpose. Since schema coverage is 0%, this description compensates adequately for the single 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 clearly states the tool deletes a scene, using a specific verb ('Delete') and resource ('a scene'). It distinguishes from siblings like remove_scene_item, which removes a scene item, ensuring the agent understands the target is the scene itself.

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?

No guidance is provided on when to use this tool versus alternatives, nor any context about prerequisites or consequences. The description does not mention that deletion is permanent or that associated scene items may be affected, leaving the agent without decision-making support.

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