add_node

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

The description only states 'Add a node' with no disclosure of side effects, permissions, or behavioral traits like whether it modifies the scene file, requires the scene to be loaded, or what happens with optional parameters. Annotations provide no additional behavioral hints (no readOnlyHint or destructiveHint).

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 concise sentence with no wasted words. However, it sacrifices informativeness for brevity, which is acceptable but not excellent.

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?

Despite having 6 parameters (including a nested object) and no output schema, the description is extremely brief. It does not explain key aspects like parent node path handling, property constraints, or return behavior, leaving significant gaps.

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 each parameter, so the baseline is 3. The tool description adds no extra semantic meaning beyond what the schema already provides.

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 'Add a node to an existing scene' clearly identifies the action and resource, but does not differentiate from sibling tools like game_spawn_node or modify_scene_node, which may have overlapping functionality.

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. There is no mention of prerequisites, such as whether the scene must be open, or when to prefer game_spawn_node over add_node.

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