geonodes_create

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

No annotations exist, so the description bears full burden. It omits behavioral details like whether it modifies the object's modifier stack, if it's safe (non-destructive), or what happens to existing node trees. Only states basic creation with a new node tree.

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?

Description is very short and includes an args section, but no superfluous content. Could be more informative without sacrificing conciseness.

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 2 parameters, no output schema, and no annotations, the description is incomplete. It doesn't mention return value, side effects, or how it fits with sibling geometry nodes 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?

Schema coverage is 0%, so description must add substantial meaning. It merely restates parameter names with short phrases ('Target object', 'Name for the node tree') without explaining constraints (e.g., object must exist, tree_name default behavior). Insufficient to compensate for lack of schema descriptions.

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 action (create), the resource (Geometry Nodes modifier), and the target (an object). It distinguishes from sibling tools like geonodes_add_node (adds node to existing tree) and add_modifier (generic 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?

No guidance on when to use this tool versus alternatives like geonodes_add_node or add_modifier. No prerequisites or context provided about existing modifiers or object state.

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