add_fillet

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

With no annotations, the description must convey behavioral traits. It offers none—no mention of mutability, document modification, or requirements (e.g., selected edges). The tool's impact on the model is entirely opaque.

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 extremely concise but not in a helpful way. It lacks any structure, front-loading, or substantive content. A single sentence that is merely a label is not conciseness but under-specification.

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 complexity of a 3D modeling tool (with 3 parameters, no annotations, no output schema), the description is completely inadequate. It omits essential context such as how edge indices are used, what happens when edge_indices is empty, and whether the operation is reversible.

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 input schema provides 100% coverage with clear parameter descriptions. However, the tool description adds zero semantic value beyond the schema. The description could hint at edge selection behavior or default radius usage, but it does not.

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 'FreeCAD tool: add_fillet' is a tautology that merely restates the tool name. It does not clarify that this tool creates a fillet on edges of a 3D object, nor does it distinguish from sibling tools like add_chamfer.

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 usage guidelines are provided. The description fails to indicate when to use add_fillet versus alternatives such as add_chamfer or other edge modification tools.

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