blender_geonode_deform_curve

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

No annotations exist, so the description must disclose side effects, but it only states that the mesh is stretched or fitted along the curve. It doesn't say whether the operation modifies the object in place, adds a modifier, requires an existing Geometry Nodes setup, or what the result/return is.

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 tight sentences with the operation first, behavior second, and use cases last. No filler or repetition; every sentence earns its place.

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?

With no output schema and no annotations, the description leaves important operational context missing: effect on the existing object, modifier behavior, return value, and any prerequisites. The full parameter schema helps, but the operation-level context is not complete.

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 covers 100% of parameters with useful descriptions, so the baseline is 3. The tool description adds no parameter-level meaning beyond the schema, but it doesn't need to because the schema is sufficient.

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?

States a clear verb-resource pair: deform a mesh along a curve using Geometry Nodes, so an agent knows what the tool does. However, it doesn't explicitly distinguish itself from siblings like blender_curve_to_mesh or blender_array_along_curve, only from the general task space.

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 'Useful for roads, rails, cables, and profile sweeps' line gives concrete contexts, so usage guidance is more than absent. It never names alternatives or when-not conditions, so the guidance is implied rather than explicit.

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