Create Spline

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

The description matches the annotation readOnlyHint=false, confirming it is a write operation. However, it adds no additional behavioral context such as permission requirements, side effects, or error conditions beyond what annotations already indicate.

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, self-contained sentence that is clear and free of unnecessary words. It efficiently communicates the essential information without redundancy.

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 that an output schema exists (so return values are covered) and the input schema is fully documented, the description provides a complete enough summary. It could offer slightly more context on when a spline is preferred over other curves, but it is largely sufficient.

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?

All three parameters have descriptions in the input schema (100% coverage), so the description adds no additional meaning. The baseline of 3 is appropriate as the schema already provides sufficient parameter semantics.

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'), the resource ('NURBS spline curve'), and the specific method ('passing through the specified fit points'). This effectively distinguishes it from sibling entity creation tools like entity_create_line or entity_create_circle.

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 implies usage for creating a spline with fit points but does not provide explicit guidance on when to use this tool versus alternatives (e.g., polyline or arc). No when-not-to-use or context for selection is given.

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