curve_create_nurbs

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

No annotations provided. The description adds some behavioral context (e.g., order_u range 2-6, w weight default 1.0) but does not discuss side effects, permissions, or creation behavior (e.g., where the curve appears).

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?

Concise and well-structured as a docstring with Args. Every sentence adds value; no redundancy or fluff.

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 creation tool with no output schema, the description covers key parameters but omits behavior like return value or how the curve integrates into the scene (e.g., added to active collection). Lacks full context for an agent.

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% (no descriptions in schema), so the description carries full burden. It explains each parameter, including details ('w = weight, default 1.0' for points, 'order_u (2-6)'), adding significant meaning beyond schema titles.

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 'Create a NURBS curve.', specifying the verb and resource. It distinguishes from siblings like curve_create_bezier by explicitly naming the curve type (NURBS).

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 (e.g., curve_create_bezier, curve_create_circle). An agent cannot determine context for preferring NURBS over other curve types.

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