save_document

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

With no annotations, the description must disclose behavior, but it only says 'save document'. It does not mention that this is a write operation, whether it overwrites, what format is used, or if it triggers a dialog.

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 short but not helpful; it is under-specified rather than concise. It is front-loaded but content is nearly useless.

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?

For a tool that performs a destructive write operation, with no annotations or output schema, the description is woefully incomplete. It should mention saving the current document, file format, potential overwrite behavior, etc.

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 100% (one parameter described). The description adds no additional meaning beyond the schema's 'Save path (optional)'. Baseline is appropriate.

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: save_document' is almost a tautology, stating the name and context but not explaining what saving a document involves. It fails to distinguish from other FreeCAD tools that also manipulate documents.

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 guidance is provided on when to use this tool, whether it should be used to save the active document, or what prerequisites exist. Sibling tools like 'export_file' are not mentioned as alternatives.

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