blender_geonode_create_group

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

With no annotations present, the description carries the behavioral disclosure burden. It usefully states that Geometry input/output sockets are automatically added and that the tool returns the group name and socket layout, which gives the agent a clear picture of the side effects and result.

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?

Three short sentences, each adding distinct value: what is created, the automatic socket behavior, and the return value. No filler or redundant restatement of schema details.

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 creation tool with no output schema, the description adequately covers the essential behavior and return value. It does not mention name-collision behavior or how to subsequently use the created group, but the information needed to call the tool and interpret its result is present.

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 already documents all parameters with 100% coverage, so baseline is 3. The description adds meaning by clarifying that the provided inputs and outputs are 'extra' beyond the automatically added Geometry sockets, which helps the agent correctly populate the optional arrays.

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 ('Create') and resource ('Geometry Nodes node group'), and adds that inputs/outputs are typed. It clearly distinguishes this from the nearby material_node_group_create tool by naming the resource explicitly.

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 no guidance on when to use this tool versus alternatives, such as material_node_group_create or the other geonode tools. The agent must infer usage from the tool name and sibling context rather than from explicit direction.

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