reset_scene_clean

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

The description adds meaningful behavioral context beyond the destructiveHint annotation by specifying exactly what gets cleaned (meshes, materials, textures) and by clarifying that it does not call read_factory_settings, which is the sandbox-safe property. It does not contradict the destructiveHint; cleaning scene content can still be destructive to the current scene while being safe to run in a sandbox.

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, front-loaded sentence that conveys the action, the affected resources, and the key safety qualifier without any filler. Every part earns its place.

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 zero-parameter, no-output-schema tool, the description adequately covers what the tool cleans and its sandbox-safety caveat. It does not elaborate on the exact destructive consequences or return behavior, but for this simple tool the core invocation context is present.

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 zero parameters and 100% schema description coverage, so the baseline is 4. The description does not add parameter information, but none is needed.

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 states a specific verb ('Limpia') and the affected resources ('mallas/materiales/texturas'), making the tool's primary function clear. The parenthetical about not using read_factory_settings hints at a distinguishing behavior, but it does not explicitly name or contrast a sibling like scene_clean, so it stops short of full sibling differentiation.

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 phrase 'sandbox-safe' implies this tool is appropriate when a non-destructive-to-session clean is needed, and 'sin read_factory_settings' suggests it avoids factory-reset side effects. However, it does not explicitly say when to prefer this over scene_clean or other cleanup tools, nor does it list any exclusion conditions.

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