geonodes_add_node

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Add a node', without mentioning what happens on success/failure, whether the tree is modified, or if there are side effects. For a mutation tool, this is insufficient.

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-line summary followed by a parameter list. It is front-loaded and easy to scan. The examples for node_type are helpful but could be separated more clearly.

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 the moderate complexity and absence of an output schema, the description should explain what the tool returns (e.g., the created node) and any prerequisites (e.g., existence of the tree). It does not, leaving the agent without key information to use the tool effectively.

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?

With 0% schema description coverage, the description adds minimal meaning: it names each parameter and gives brief context (e.g., 'Blender node type (e.g., GeometryNodeMeshPrimitiveCube...)'). However, it does not specify constraints or formats for 'location' or 'name' beyond the schema types, so it adds only limited value.

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 'Add a node to a Geometry Nodes tree', specifying the verb 'add', the resource 'node', and the context 'Geometry Nodes tree'. This distinguishes it from sibling tools like geonodes_create (creates the tree) and geonodes_connect (connects 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 provides no explicit guidance on when to use this tool versus alternatives, or any prerequisites. It is implied that the tree must already exist and that the user wants to add a node, but no exclusions or context are given.

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