object.create_curve

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

Annotations provide no positive hints (all flags false), so the description must carry behavioral disclosure, but it only reports 'Risk: standard; maturity: L3' and 'session policy' constraints. It does not mention side effects, whether the operation mutates the scene, or what happens on success/failure.

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 text is short, but shortness here is under-specification rather than conciseness. It front-loads only metadata and leaves out the core behavioral sentence that would make the entry useful.

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 six-parameter creation command operating in a large sibling toolset, the description is far from complete: no purpose, no usage, no parameter guidance, no behavioral detail. The output schema exists but does not compensate for the missing selection and invocation context.

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 only 50% and the description adds no parameter meaning. 'name' and 'bevelDepth' are the key domain parameters but are undocumented in the schema and unmentioned in the description, leaving an agent to guess their formats.

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 only restates the command identifier 'object.create_curve' and adds risk/maturity metadata; it never states that this creates a curve object or what inputs affect that creation. It does not distinguish this tool from the sibling blender_curve_create, which appears to target the same object type.

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?

There is no statement of when to use this tool instead of alternatives such as blender_curve_create, object_create_mesh, or object_create_text. The only usage-like sentence is a generic harness policy note that applies to every command.

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