add_sketch_fillet

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

Discloses that it replaces vertex with arc, requires sketch edit mode, and that lines must be adjacent. Mentions it returns metadata. No annotations provided, so description carries the burden and does it well.

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 bilingual (Spanish and English) which adds length, but is well-structured and front-loaded with key information. Every sentence adds value.

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 no output schema, the description mentions it returns metadata. It covers preconditions (edit mode, adjacent lines), differentiates from siblings, and provides typical usage example.

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% coverage, so description fully explains each parameter: line1_x_mm and line1_y_mm are points on the first line near the corner, similarly for line2, radius_mm is the fillet radius, and z_mm is Z-coordinate with default 0.

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 rounds a sketch corner with a tangent arc, replacing the vertex. It distinguishes itself from create_arc and add_sketch_chamfer, and mentions typical use (CSWA Tool Block).

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?

Describes when to use (rounded corners, CSWA Tool Block) and compares to alternatives (chamfer, manual arc). Does not explicitly list exclusions or when not to use, but provides sufficient context.

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