add_sketch_fillet

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

No annotations provided, so description carries full burden. It explains destructive behavior (replaces vertex with arc), that SW picks closest segment, and constraints (adjacent lines). Returns metadata. Good coverage for a simple tool.

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?

Description is concise and front-loaded. The English portion is efficient, two sentences followed by a usage note and parameter explanations. No redundant information.

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?

With 6 parameters and no output schema, the description covers purpose, parameter semantics, prerequisites (edit mode), constraints (adjacent lines), and related tools. Sufficient for correct 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?

Schema has 0% description coverage; description adds meaning for all 5 required params: explains that line1_x_mm/line1_y_mm are points on first line near corner, similarly for line2, radius_mm is fillet radius, z_mm is Z-coordinate default 0. Fully compensates for lack of schema descriptions.

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 it rounds a sketch corner with a tangent arc between two adjacent lines, replacing the vertex. It includes a typical use case (CSWA Tool Block R3) and distinguishes from siblings add_sketch_chamfer and fillet.

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 context: sketch must be in edit mode, lines must be adjacent, and gives a typical use case (R3). Mentions related tools. Lacks explicit when-not-to-use but is informative about requirements.

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