clearScene

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

With no annotations provided, the description carries the full burden. It discloses that the tool removes objects and resets lighting, indicating a destructive operation. However, it lacks details on permissions, reversibility (e.g., via undo), or effects on non-user objects, which are important for a mutation 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 a single, efficient sentence that front-loads the main action ('Remove all user-created objects') and includes an additional effect. Every word earns its place, with no redundancy or unnecessary elaboration.

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?

Given the tool's complexity (destructive reset), no annotations, and no output schema, the description is minimal but covers the core action. It lacks details on what 'user-created objects' entails, whether default lighting is configurable, or error conditions, making it adequate but with gaps for safe use.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, but it could have mentioned any implicit parameters or side effects, though not required. Baseline is 4 for zero parameters.

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 specific action ('Remove all user-created objects') and the resource ('from the scene'), and distinguishes it from siblings like deleteObject (which removes individual objects) or loadScene (which resets to a saved state). It also includes an additional effect ('reset default lighting'), making the purpose comprehensive and specific.

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 when a full scene reset is needed, distinguishing it from tools like deleteObject for selective removal. However, it does not explicitly state when not to use it or name alternatives, such as loadScene for reverting to a saved state, leaving some ambiguity in context.

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