create_geometry_nodes

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

The description discloses the main side effect of creating both a modifier and a node group with a direct Group Input to Output connection. However, it does not mention default naming behavior, potential conflicts, or what happens if optional parameters are omitted.

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 a single concise sentence with no redundant information. It efficiently conveys the core action and the included direct connection.

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 is too sparse for full context. It does not mention default values, return behavior, error conditions, or how this tool fits with the broader set of geometry node and modifier tools.

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 provides no parameter descriptions, and the description only gives a minimal implication that 'object' is the target. 'group_name' and 'modifier_name' are inferable from naming conventions but are not explicitly explained.

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 the tool creates a new geometry node modifier and node group on an object, including a Group Input to Output direct connection. This distinguishes it from related tools like add_geometry_node or add_modifier.

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 explains what the tool does but provides no guidance on when to use it versus alternatives such as add_geometry_node, build_geometry_node_tree, or add_modifier. No explicit usage context or exclusions are given.

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