create_curve

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

Basic creation behavior is clear, but with no annotations, the description doesn't reveal side effects (e.g., whether object is added to scene, coordinate system, error handling). It explains point format and a few settings, but not overall behavior.

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?

Efficient four-sentence description with front-loaded purpose. No unnecessary words; each sentence adds vital information. Well-structured.

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?

Handles key parameters but missing extrude, resolution, and name. Lacks output details (no output schema) and operational context (scene placement, default behavior). Adequate but not fully comprehensive for a creation tool with 8 parameters.

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 description explains points format, bevel_depth, close, fill, and type, adding value beyond the raw schema (0% coverage). However, it omits extrude, resolution, and name parameters, leaving gaps.

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 the tool creates a curve from control points and lists available types (BEZIER, NURBS, POLY). This differentiates it from sibling curve tools that are more specialized (e.g., curve_create_circle), but it does not explicitly contrast them.

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 vs. alternatives like curve_create_bezier or curve_create_nurbs. The description explains how to configure parameters but lacks context for tool selection.

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