geometry-set_bezier_spline

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

With no annotations available, the description must disclose behavioral traits but does not. It only states 'Replace a curve's spline with bezier control points' without mentioning side effects, requirements (e.g., curve type), or any consequences for existing handles. The phrase 'the modeling curve' is unclear and adds no transparency.

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 extremely brief (one sentence), but it is not well-structured; it ends with a fragment 'the modeling curve' and lacks coherent structure. It is concise but at the expense of clarity.

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 the complexity of the operation (setting bezier splines with handles and closure), the absence of output schema, annotations, and detailed parameter descriptions makes this description severely incomplete. It does not explain input formats, handle types, or the effect of 'closed'. This is inadequate for an AI agent to use correctly.

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%, so the description must explain parameters, but it does not. It mentions 'bezier control points' which loosely maps to 'points' but provides no explanation for 'object', 'handles', or 'closed'. The description adds no meaningful semantic value beyond the schema 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 states a specific action ('Replace a curve's spline') on a specific resource ('curve's spline'), which distinguishes it from sibling tools like geometry-set_curve that likely handle other curve properties. While the phrase 'the modeling curve' is ambiguous, the overall purpose is clear.

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. The description does not mention prerequisites, preferred contexts, or differences from similar tools like geometry-set_curve. Users must infer usage solely from the name.

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