blender_curve_create

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

With no annotations provided, the description must carry the behavioral burden, and it does convey the main side effect: a new curve object is created from the supplied control points. However, it does not disclose scene-level effects such as object naming, placement defaults, or return behavior, leaving gaps for an agent to infer.

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 two sentences with no redundancy: the first states what the tool creates and its input, and the second justifies when curves are useful. It is front-loaded with the operation and immediately actionable.

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?

For a 7-parameter creation tool with no annotations or output schema, the description is adequate but not complete. The schema compensates for parameter details, yet an agent still lacks explicit information about the result of the operation or how the new curve integrates with the current scene/collections.

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 already documents all seven parameters with 100% coverage, so the baseline is 3 because the description does not add parameter-specific detail. It only reinforces the 'control points' concept already present in the schema.

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 a specific action ('Create') and resource ('a Bezier, NURBS, or Poly curve...from control points'), which is enough to understand what the tool does. It does not explicitly reference sibling tools like blender_curve_from_mesh_edge or blender_curve_to_mesh, so sibling differentiation relies mostly on the 'from control points' phrase.

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 second sentence gives concrete use cases ('smooth profiles, body panels, pipe routing, and organic shapes'), providing clear context for when curve creation is appropriate. It does not offer exclusions or explicitly point to alternative mesh/curve tools, so it stops short of full when/when-not guidance.

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