instance_scene

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

Annotations only provide readOnlyHint=false and destructiveHint=false. The description adds the behavioral detail 'undoable', which is valuable for mutation operations. It also specifies it adds the instance as a child in the open scene, providing context beyond annotations. No contradiction with 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?

Single, well-structured sentence that front-loads the action and resource. Every word contributes meaning with no redundancy or fluff.

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?

Tool has 3 parameters and no output schema. The description is too brief to cover important context: no explanation of the 'parent' parameter (where to attach? root by default?), no mention of behavior on invalid paths, no return value. The 'undoable' note is helpful but insufficient for a mutation tool with multiple parameters.

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?

Input schema has 3 parameters with 33% description coverage (only scene has a description). The description reinforces the scene parameter by mentioning 'packed scene (res://*.tscn)', but does not explain the 'name' or 'parent' parameters. Baseline at 3 due to partial schema coverage, and the description adds some but insufficient value for the undocumented parameters.

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 verb 'Instantiate', the resource 'packed scene', and the context 'as a child in the open scene'. It distinguishes from sibling tools like create_node or open_scene by specifying it's for instantiating .tscn/.scn files.

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 explicit guidance on when to use this tool versus alternatives, nor any exclusion criteria. The phrase 'in the open scene' implies a prerequisite that the scene must be open, but this is not stated explicitly. No when-not-to-use or alternative tool references.

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