blender_curve_to_mesh

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

With no annotations provided, the description carries a heavier burden. It usefully explains that bevel_depth creates a tube and extrude creates a flat panel, but it does not disclose whether the original curve is replaced/destroyed, what happens when apply_as_mesh is false, or how the two modes interact if both parameters are set.

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 wasted words. The core action is front-loaded, and the mode distinction is explained immediately.

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 essential purpose and mode selection are clear, and the schema documents all seven parameters. However, with no annotations and no output schema, the description misses important behavioral caveats such as the effect of apply_as_mesh=false and the ambiguity when both bevel_depth and extrude are set.

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 100%, so the baseline is 3. The description adds meaningful conceptual meaning beyond the schema labels by mapping bevel_depth to 'tube' and extrude to 'flat panel', which helps an agent choose the right parameter values.

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 states a specific operation, 'Convert a curve to mesh', and names two concrete output modes, bevel (tube) and extrude (flat panel). This clearly distinguishes the tool from curve creation, mesh editing, and geonode curve tools.

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 gives clear context that this is for converting curves into meshes and even guides the agent between bevel tube and extrude flat panel modes. It does not explicitly name alternatives or when-not-to-use cases, so it stops one step short of a 5.

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