sketch_arc

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

No annotations provided, so the description carries the full burden. It fails to disclose behavioral traits such as whether the arc is created as a sketch entity, any default direction, or how it integrates with sketch constraints. Minimal 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 a single sentence that is direct and to the point. No wasted words, but it could be slightly expanded without harming 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 lack of annotations, output schema, and five parameters, the description is insufficient. It does not explain the arc geometry type, direction defaults, or prerequisite state (active sketch). Incomplete for confident use.

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?

The description adds no value beyond the schema. While the schema provides descriptions for sub-properties (e.g., Center X coordinate), the tool description does not explain parameter roles or relationships (e.g., center, start, end points define the arc). Only the 'construction' parameter has a schema description.

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 verb (Draw) and resource (arc) and specifies it operates in the active sketch. It distinguishes from other sketch tools like sketch_line or sketch_circle, but does not specify the arc type (center-start-end).

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 versus other sketch tools. No mention of prerequisites (e.g., an active sketch must exist) or alternative tools like sketch_ellipse for curved shapes.

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