add_scene_instance

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic action without revealing side effects (e.g., if it modifies the current scene permanently), required permissions, error conditions, or return value. The agent lacks understanding of the tool's impact.

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?

A single sentence of 16 words with no redundancy. Every word is necessary and the description is front-loaded with the key action. It efficiently conveys the 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?

For a 2-parameter tool with no output schema, the description is too minimal. It omits what happens on success/failure, default behavior for parent_path, and whether the scene must be pre-loaded. Critical context for a mutation tool is missing.

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 both parameters described in the schema. The tool description adds no additional meaning beyond the schema, which already defines 'scene_path' and 'parent_path' clearly. Baseline 3 applies as the schema does the work.

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 'Add' and resource 'instance of a scene' and specifies the action 'as a child of a node'. It clearly distinguishes from sibling tools like 'add_node' (adds a node type) and 'add_mesh_instance' (adds a mesh).

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 implies when to use the tool (when you need to instantiate a scene file as a child), but does not explicitly state when not to use it or suggest alternatives like 'add_node' for adding a blank node. No exclusion criteria provided.

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