export_freecad_stl

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the CAD document is not altered, which is important safety context, but it omits file-write behavior, overwrite semantics, required document state, and any permission or selection prerequisites.

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 definition is a single front-loaded sentence with no filler or repetition. Every phrase contributes to purpose or scope.

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?

Although an output schema exists, so return values need not be explained, the description is thin for a tool with no annotations and 0% schema coverage. It leaves both required parameters and the file-writing behavior largely undocumented.

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 description coverage is 0%, so the description must explain the parameters, but it does not. It hints that object_name refers to a selected FreeCAD object, but the required path parameter is never described in terms of format, destination, or overwrite behavior.

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 states a specific verb and resource: export a FreeCAD object to STL. It also scopes the operation to one selected object and clarifies non-mutation of the CAD document. An agent can easily distinguish this from inspection, slicing, or setup siblings.

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?

It implies the tool is used to create an STL file, but gives no explicit when-to-use guidance, prerequisites, or alternatives. There is no mention of when to choose export_freecad_stl versus inspect_freecad_document, preview_slice, or run_slice.

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