node_create

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

No annotations provided, so description carries full burden. It clarifies creation modes and parent path semantics but omits details on error handling, return values, or immediate addition to scene tree. Adequate but not comprehensive.

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 with clear purpose and key details. No redundancy or filler. Efficiently communicates core functionality.

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 6 parameters, the description covers the two key creation modes and parent_path semantics. Output schema exists but unknown. For a node creation tool, it sufficiently explains the main logic, though could mention return value briefly.

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%, but description adds meaningful context: explains type vs scene_path mutual exclusivity, and that parent_path is relative to edited scene root (not runtime). This goes beyond schema definitions.

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 states 'Create (spawn) a new node in the scene tree' with specific verb 'create' and resource 'node'. It distinguishes between creating via type and instantiating a PackedScene via scene_path, clearly differentiating the tool's core function.

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 implicitly guides usage by explaining the mutual exclusivity of type and scene_path, and parent_path being relative to edited scene root. However, it lacks explicit when-to-use vs alternatives or exclusions, which is acceptable given the sibling tools have distinct purposes.

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