geometry_nodes_create

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

The description discloses the core behavior of creating a modifier with either a new or existing node group. However, it does not explain what happens when node_group_name is empty, whether the modifier is appended or replaces an existing one, or error behavior. Annotations only provide destructiveHint=false, so the description carries some burden but fills only part of it.

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?

A single sentence, front-loaded with the action and resource, containing no filler. It is appropriately concise for a tool of this simplicity.

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 tool is simple enough that the description covers the main action, but critical gaps remain: how node_group_name is interpreted when empty, what object it applies to, and whether a new node group is auto-created. With no output schema and sparse annotations, an agent may need to infer important invocation details.

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 description coverage is 0%, so the description must compensate for the three parameters. It lightly hints at the role of node_group_name ('new or existing node group') but does not clarify object_name requirements, modifier_name defaults, or the semantics of an empty node_group_name. This is insufficient for a 3-parameter tool with no schema documentation.

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 a specific verb ('Create') and resource ('Geometry Nodes modifier') and distinguishes the tool from generic modifier tools like add_modifier and from geometry_nodes_add_node/link/set_param. The phrase 'with a new or existing node group' adds meaningful scope.

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 is given about when to choose this tool over alternatives such as add_modifier or geometry_nodes_templates. The description implies its own obvious use case but does not provide exclusions, prerequisites, or selection criteria.

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