Export model to FreeCAD

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

No annotations are provided, so the description carries the full burden. It discloses that the tool runs headless and gives a time estimate, but does not explain side effects (e.g., whether it modifies the model), required permissions, or error handling. Adequate but not thorough.

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?

Two sentences: first states purpose and content, second gives runtime and execution method. No extraneous words, front-loaded with key 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?

Given no output schema and a simple task, the description covers the main functional aspects. It mentions runtime and headless execution, but lacks details on failure modes or prerequisites (e.g., model must exist). Still, it is mostly complete for this tool.

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 coverage is 50%; the path parameter has a description, model does not. The description adds context about the default path and export format but does not explain the model parameter beyond being required. The description partially compensates for missing schema details.

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's purpose: 'Build a solid 3D representation...and save it as a FreeCAD .FCStd document'. It uses specific verbs and resources, and distinguishes it from sibling tools like export_calculix_inp which exports to a different format.

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?

The description provides context (headless freecadcmd, ~5-20 s) and implies when to use (for FreeCAD export vs. other export formats). It does not explicitly state when not to use or provide alternatives, but the purpose is clear enough.

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