create_curve

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

No annotations are provided, so the description must carry behavioral disclosure. It only says 'Create a new curve object' without explaining side effects (e.g., object is added to the active collection), permissions needed, or whether it can overwrite existing objects.

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 four sentences with no fluff: one main sentence, args listed concisely, and a returns line. It front-loads the core action and efficiently conveys parameter details.

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?

While the description covers the basic purpose and parameters, it lacks context such as where the curve is created (e.g., active scene/collection) and does not mention the default type (BEZIER). The presence of an output schema is noted but not detailed in the description. With no annotations, more behavioral context would improve completeness.

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 input schema has 0% description coverage, but the tool description provides meaningful explanations for all three parameters: type (with enum list), name (optional), and location (3D coordinates). This adds significant value beyond the bare schema titles and defaults.

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 new curve object' and enumerates the supported curve types (BEZIER, NURBS, or PATH). This differentiates it from sibling tools like add_curve_point (which modifies existing curves) and create_object (generic object creation).

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 implicitly sets usage context by listing arguments and return type, but it does not explicitly state when to prefer this over alternatives (e.g., create_object) nor provide exclusion criteria (e.g., prerequisites like having an active scene).

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