sketch_spline

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

No annotations are present, so the description bears full responsibility. It only states the action without disclosing behavioral traits such as whether the spline is created in the active sketch, what happens if no sketch is active, or if points must be in the sketch plane. This is insufficient for safe invocation.

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, well-structured sentence that quickly conveys the core purpose. It is front-loaded and efficient, though it could be more informative without losing 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 the complexity of sketch operations and the presence of many sibling tools, the description lacks important context. It does not mention that the spline is added to the active sketch, that points are relative to the sketch origin, or that closed/construction are optional. The schema provides parameter details but the tool description misses environmental prerequisites.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema; it does not provide context for 'points' (e.g., coordinate system, unit assumptions) or 'closed'/'construction' (e.g., effect on geometry).

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 uses the specific verb 'Draw' and identifies the resource as 'a spline through points in the active sketch'. This clearly differentiates it from sibling tools like sketch_line (draw line segments) and sketch_circle (draw circles).

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 provides no guidance on when to use this tool versus alternatives. Among siblings like sketch_line, sketch_circle, etc., there is no mention of use cases, prerequisites (e.g., active sketch required), or exclusions.

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