create_curve

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states 'Create a curve object' and lists types; it does not mention side effects, coordinate space, default naming/location behavior, or whether prior selection matters. For a mutation tool, this is minimal.

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?

A single, front-loaded sentence with no filler. The essential information—action, resource, and type options—is delivered efficiently.

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 3-parameter creation tool with no annotations, the description is too sparse. It does not explain how location is interpreted, whether name is a unique identifier, or what the output of the operation is (though an output schema exists). The type list helps, but the overall guidance is incomplete.

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%, so the description must compensate. It does cover the 'type' parameter by listing allowed values, but it says nothing about 'name' or 'location'. Even the type list lacks details like default behavior or format restrictions beyond what the schema enumerates.

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 action ('Create') and the resource ('a curve object'), and enumerates the valid types (BEZIER, NURBS, POLY). This adequately distinguishes it from modification tools like set_curve_property or set_curve_points, though it doesn't explicitly contrast with generic create_object.

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 about when to use this tool versus alternatives like create_object or set_curve_property. The intended use case is implied by the name and description, but there are no explicit conditions, prerequisites, or exclusions.

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