geometry-create_curve

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

With no annotations, the description must disclose behavioral traits, but it only states 'Create a curve primitive'. It doesn't mention side effects (e.g., adding an object to the scene), required permissions, or any constraints. This is insufficient for a tool that creates an object.

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 a single concise sentence with no fluff. It is front-loaded and to the point. However, it is overly brief, which might undercut its utility, but for what it says, it is appropriately sized in terms of conciseness.

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?

Given 6 parameters, no annotations, no output schema, and 0% schema coverage, the description is severely incomplete. It fails to explain what curve types are available, how parameters affect the result, or what the created object looks like. A one-liner is far from sufficient for this tool's complexity.

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 description coverage is 0%, and the description provides no information about parameters like 'name', 'type', 'scale', 'radius', 'location', or 'rotation'. The description does not compensate for the lack of parameter documentation; the agent must rely solely on the schema, which lacks semantic detail beyond 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 the tool creates a curve primitive with a specific verb ('Create') and resource ('curve primitive'). It distinguishes from sibling tools like geometry-create_text or geometry-create_surface, though it doesn't explicitly differentiate from geometry-set_curve (which modifies existing curves). The purpose is clear but could be more specific about the primitive types.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or exclusions. The description is a single sentence with no context for selection.

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