cad_sketch_arc

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

Describes geometric behavior (counterclockwise sweep, radius set by start, end snaps to radius) and construction mode, but does not mention prerequisites like active sketch.

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 with clear, front-loaded purpose and no unnecessary 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?

Covers return value and parameter behavior; missing only sessionId context and edge cases, but adequate given sibling tool consistency.

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?

Adds meaning to center, start, end, and construction parameters beyond schema; explains radius derivation and return value access. SessionId is standard and not described.

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?

Clearly states it adds a center-point arc swept counterclockwise from start to end, returns entityId, and distinguishes from other sketch tools by specifying geometry behavior.

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?

Provides explicit guidance on using swap start/end for complementary arc and construction flag for reference arcs, but does not explicitly state when not to use.

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