blender_geonode_apply

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

With no annotations, the description carries the full transparency burden. It does well by disclosing that the operation is non-destructive (adding a modifier, not baking/apply), that inputs can optionally be set, and that it returns the modifier name and current input state. It does not cover edge cases like object-type restrictions or error behavior, but core behavioral disclosure is present.

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?

Two sentences with no fluff. The main action and the return value are both stated efficiently and in a logical order.

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 covers the essential context: what is being done, the optional input behavior, and what is returned. Since there is no output schema, the explicit return description is valuable. It could be more complete by mentioning prerequisites or failure modes, but it is sufficient for typical use.

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 input schema already documents all three parameters with descriptions and accepted value types, so the description adds little beyond noting that inputs are optional. This is the expected baseline given 100% schema coverage.

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 identifies the action: apply an existing Geometry Nodes group to an object as a modifier, with optional input value setting. It distinguishes this from tool siblings like blender_geonode_create_group (which creates the group) and blender_modifier_add/configure (which handle modifiers more generically).

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 makes the usage context clear: use this when you already have a Geometry Nodes group and want to attach it to an object as a modifier. It does not explicitly name alternative tools or state when not to use it, but its purpose is specific enough to guide selection.

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