instantiate_scene

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

With no annotations, the description carries full burden. It only states the basic action without disclosing behavioral traits such as whether the scene is loaded from a path, what happens if the scene is already loaded, or if there are any side effects on the existing scene tree.

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 sentence with no extra words, but it is too brief for the tool's complexity. While concise, it sacrifices essential information that an agent would need.

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 lack of annotations, output schema, and parameter coverage, the description is severely incomplete. It fails to provide sufficient information for correct invocation, handling input constraints, or understanding outcomes.

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 has 3 parameters with 0% coverage. The description does not explain any parameter meaning, format, or constraints. For example, 'scene_path' could be a file path or resource path, and 'node_name' is optional but not clarified.

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?

Description clearly states the action (instantiate), resource (PackedScene), and target (current scene). However, it does not differentiate from sibling tools like add_node or create_scene, which could also involve adding nodes. The wording is unambiguous but lacks distinguishing specificity.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, side effects, or scenarios where instantiate_scene is preferable to similar tools like add_node or load_resource. The agent is left without context.

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