fusion_sketch_spline

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

Annotations already indicate non-readonly and open world; description adds no further behavioral details (e.g., does it add to active sketch? any side effects?). Minimal value beyond annotations.

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?

Single, clear sentence. Could be split for readability but efficiently conveys core info. No wasted words.

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?

Missing key context for a 5-param tool: no mention of which sketch the spline is added to, no output description, no details on plane or sketch parameters. Incomplete for reliable usage.

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?

With 0% schema coverage, description adds meaning for points (format [[x,y],...] and unit mm), type (lists options), and degree (states it uses it). However, plane and sketch parameters are not explained, and points array item type is ambiguous.

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?

Description clearly states action 'Draw a spline', resource 'through points [[x,y],...] (mm)', and mentions type options and degree. Distinguishes from sibling sketch tools (e.g., fusion_sketch_line, fusion_sketch_circle) by being the only spline tool.

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 on when to use this tool vs alternatives (e.g., other sketch curves), no prerequisites (e.g., need a sketch), and no contrast between fit_points vs control_points. Lacks context for optimal usage.

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