autocad_save_document

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: output format is backend-dependent (ezdxf writes '.dxf', COM writes '.dwg'), which the agent cannot infer from annotations or schema.

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?

Front-loads the core action in one sentence, then uses Args/Returns blocks so the optional parameter and result shape are easy to scan. Slightly verbose for a one-parameter tool but nothing is wasted.

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?

An output schema exists, so the Returns line is a bonus rather than a necessity, and annotations already carry the safety profile. The backend-dependent extension and the re-save semantics give an agent enough to invoke this correctly; only the never-saved-drawing failure case is left out.

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 reported at 0%, so the description carries the param burden and does so: it marks 'path' optional, explains the omit-to-resave behavior, and notes the extension differs per backend. It omits one nuance present in the schema — that omitting path fails on a never-saved drawing — but otherwise compensates well for the coverage gap.

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?

Names a specific verb and resource ('Save the active drawing to disk'), which cleanly separates it from open_document, new_document, and the query/edit siblings. No explicit sibling routing, but the purpose is unambiguous without opening any schema.

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?

Provides the parameter-level usage rule ('omit to re-save to the current path'), which is useful context for the single optional arg. However, it never states when this tool should be preferred over alternatives or what prerequisites exist (e.g. an active/initialized drawing or a live COM connection); usage is only implied.

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