fusion_sketch_circle

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

Annotations indicate it's a write operation (readOnlyHint=false, destructiveHint=false). The description 'Draw a circle' adds no further behavioral context such as side effects, preview, or error handling. With annotations already clear, description adds minimal value.

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 sentence of 12 words is highly concise and front-loaded with the key action. 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?

Despite low complexity and no output schema, the description omits crucial context: the circle is added to a sketch (active or specified via 'sketch' param), and no return value or confirmation is mentioned. Incomplete for an agent to reliably invoke.

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 0%, so description must compensate. It explains that x,y are center coordinates and radius/diameter are alternatives, and specifies units (mm). However, plane and sketch parameters are not described, limiting completeness.

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 tool draws a circle in millimeters by center coordinates and either radius or diameter. This specific verb+resource distinguishes it from sibling tools like fusion_sketch_arc or fusion_sketch_line.

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 drawing circles but does not provide explicit when-to-use or when-not-to-use guidance. No mention of alternatives or conditions like using radius vs diameter.

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