foundry_switch_scene

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

Annotation readOnlyHint=false already indicates mutation. The description adds the 'player-facing' nuance, which is useful context, but it does not disclose permissions, side effects on the previous scene, or the result of the operation. Has modest added value beyond annotations.

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 six-word sentence, highly concise and front-loaded. Every word contributes without unnecessary detail.

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 tool has no output schema and zero required parameters, so the description must compensate. It fails to explain how to specify the target scene, what happens on success or failure, or whether the operation is restricted to GMs. Too sparse for a mutation tool.

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 50%, with name and sceneId lacking descriptions. The description does not add any meaning to these parameters, leaving ambiguity about which identifiers are valid and how the parameters relate. With zero required parameters, this is a notable gap.

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 uses a specific verb ('Switch') with a clear resource ('player-facing active scene'), which effectively distinguishes it from sibling tools like foundry_update_scene or foundry_get_scenes. It conveys the essential action concisely.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or related tools. It is a bare statement of the operation without contextual cues for tool selection.

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