loadScene

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'Replace[s] the entire scene', implying a destructive mutation, but does not clarify if this action is reversible (e.g., via 'undo'), what happens to existing scene elements, or any side effects like requiring specific permissions. More context is needed 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 key action ('Replace the entire scene') without unnecessary words. Every part of the sentence contributes to understanding the tool's purpose.

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 (a destructive scene replacement with one parameter) and lack of annotations or output schema, the description is adequate but incomplete. It explains the basic action but omits important behavioral details like reversibility or effects on sibling tools (e.g., interaction with 'undo'), leaving gaps for an AI agent.

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 description mentions 'previously exported scene JSON', which aligns with the 'sceneJson' parameter in the schema. Since schema description coverage is 100%, the baseline is 3, and the description adds minimal value beyond what the schema already provides (e.g., it doesn't specify JSON format details).

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 ('Replace the entire scene') with the resource ('previously exported scene JSON'), distinguishing it from siblings like 'loadSceneFromFile' (which likely loads from a file) and 'exportScene' (which exports rather than imports).

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 such as 'loadSceneFromFile' or 'clearScene', nor does it mention prerequisites like needing a scene JSON from 'exportScene' first. It lacks explicit when/when-not instructions.

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