node_create

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

With no annotations provided, the description carries the full burden. It discloses that the tool adds the node to the parent and that scene_path overrides type. This is meaningful behavioral detail beyond the obvious mutation. It omits error handling or permission requirements, but the core behavior is transparent.

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 concise: a one-sentence summary followed by a brief elaboration. Every sentence adds value, with no redundancy or filler. The information is front-loaded for quick comprehension.

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?

The description covers the primary decision (type vs scene_path) and the core creation behavior. With six optional parameters and an output schema, the description does not need to detail each parameter or return values. However, it could briefly mention prerequisites like an open scene, leaving a minor gap.

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?

The schema covers 100% of the parameters, so the baseline is 3. The description adds extra value by explaining the mutual exclusivity between type and scene_path, which is not apparent from the schema alone. This elevates parameter understanding.

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 starts with 'Create (spawn) a new node in the scene tree,' a specific verb and resource, and immediately clarifies two modes: creating by type or instantiating a PackedScene. This clearly distinguishes it from sibling tools like node_set_property or node_find, which operate on existing nodes.

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 gives clear context for when to use this tool: to add a new node to the scene tree, with explicit guidance on the two mutually exclusive modes. However, it does not name alternatives (e.g., 'for modifying an existing node, use node_set_property') or provide when-not-to-use exclusions, so it stops short of a full 5.

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