close_scene

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

No annotations are provided, so the description must reveal behavioral traits. It states the action but not consequences: whether unsaved changes are lost, whether a confirmation prompt appears, or how the save parameter affects the operation. This hides critical details for a close operation.

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, short sentence that immediately states the action. It has no fluff and is easy to parse. While it is sparse, it earns its place for what it says, though additional details are missing.

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?

With one optional parameter and no annotations, the description is insufficient. It doesn't address the parameter's effect, error handling (e.g., no current scene), or whether the operation is destructive/reversible. Given the side effects of closing a scene, the tool requires more explanatory context.

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 defines a single boolean 'save' parameter with no description (0% coverage). The description does not mention this parameter, leaving its meaning ambiguous (e.g., save before closing? choose to save?). The description adds no value beyond the schema, and the schema itself is minimal.

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 action: 'Close the current scene.' This is a specific verb and resource, and it distinguishes the operation from sibling tools like open_scene, save_scene, and create_scene. However, it doesn't mention the optional save parameter, which could blur the boundary between close and save operations.

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 tool vs alternatives. It doesn't reference sibling tools, conditions, or scenarios such as discarding changes vs saving before close. The one-line description offers no context for choosing this tool.

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