Stage Set Define

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

With no annotations, the description carries the behavioral burden well: it discloses that matched groups carry children, matched actors neither play/follow/rest while unloaded, remove=True drops the set after loading it if needed, every item must match, and state is saved in world.json with history. It leaves out permission or concurrency details, but the important side effects are covered.

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 core definition is front-loaded, and most sentences add concrete behavioral or parameter detail. It is dense and somewhat run-on, but appropriate for the complexity of the tool.

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 covers most behavioral and persistence aspects, and an output schema exists so return values need not be explained. However, the required 'scene' parameter and the 'scenes' parameter are undocumented, which is a meaningful gap for 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?

Schema coverage is 0%, so the description must explain six parameters. It gives useful meaning for name, items, note, and remove, including glob syntax and placeholder text, but completely omits the required 'scene' parameter and the optional 'scenes' parameter, leaving key invocation semantics unclear.

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 action, naming a load set that groups room elements and can later be loaded via stage_set_load. It is distinguishable from siblings like stage_sets and stage_set_load, though the theatrical metaphor ('keep the Quest light') makes the purpose slightly less immediately clear.

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?

It explicitly names the companion loading tool (stage_set_load) and explains removal via remove=True, which implies when to use it. However, it does not state clear when-to-use conditions versus alternatives or when not to use it.

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