Reset Active Scene

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

With no annotations, the description fully discloses destructive behavior: prefix removes specific items and flushes undo buffer; no prefix swaps for an empty document. It also mentions performance relative to alternatives. Minor omission: no explicit warning about data loss for full reset.

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?

Two well-structured sentences. Front-loaded with the core action, then details modes, use cases, and alternatives. Every sentence contributes meaningful information without 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?

Given no output schema, the description adequately covers behavior, modes, parameters, and performance trade-offs. No apparent gaps for an agent to invoke the tool correctly.

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 covers 100% of parameters. Description adds value by providing usage context (e.g., prefix example 'e2e_'), explaining the behavior of each parameter, and clarifying the `keep_active_rd` default. Goes beyond mere schema reproduction.

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 clears scene state in one RPC, explains two distinct modes (prefix-based partial cleanup and full reset), and distinguishes it from sibling tools like remove_entity by highlighting speed advantages for animated objects.

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?

Explicitly states when to use each mode: with prefix for test suite cleanup, without prefix for full reset. Names the alternative `remove_entity` and explains why `reset_scene` is preferable in certain scenarios.

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