load_scene

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

Annotations already provide idempotentHint=true and readOnlyHint=false. The description adds that additive loading is supported with a default false, which is useful. However, it does not disclose side effects like unloading the previous scene when additive=false, nor does it explain error conditions or folderPath resolution behavior.

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 sentences convey the essential purpose and a key behavioral option with no unnecessary words. The description is front-loaded and efficient.

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 four optional parameters and no output schema, the description covers the basic mechanism but omits important details: precedence when both scenePath and sceneName are provided, behavior when additive=false (unloads current scene), folderPath usage, and potential errors. Not fully complete for complex contexts.

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 100% with descriptions for all parameters. The description mentions loading by path or name and additive loading, but these concepts are already covered in parameter descriptions. No additional meaning is added beyond the schema.

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 'Loads a scene by path or name', which identifies the verb (loads), resource (scene), and two resolution methods. However, it does not explicitly differentiate from sibling tools like create_scene or delete_scene, so it misses some sibling distinction.

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?

No guidance is given on when to use this tool versus alternatives such as add_asset_to_scene or create_scene. The description lacks context for selecting this tool over siblings, leaving the agent to guess usage context.

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