export_drawing

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about whether an existing file at output_path is overwritten, whether the live drawing is mutated, whether parent directories must exist, or whether a connection to AutoCAD must be established first. The output schema covers return values, so that omission is acceptable, but the write-safety profile of a file-creating mutation is entirely undisclosed.

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 purpose sentence is front-loaded and the Args block is compact; since schema coverage is 0%, the parameter lines are not redundant filler. The raw docstring formatting is slightly less scannable than prose but wastes no sentences.

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 return values need not be described, and the two parameters are at least named. What is missing for a file-writing tool with zero annotations is overwrite semantics, connection prerequisites, and format/path interaction — enough gaps that an agent could call it incorrectly and silently clobber a file.

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% and the format parameter has no enum in the schema, so the description genuinely compensates by listing 'dwg', 'dxf', 'pdf', 'png' and by giving concrete path examples. However, it never states whether the path's extension must match the format, whether relative paths are accepted, or whether the target directory must already exist.

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 (save/export) plus the resource (the active AutoCAD 2027 drawing) and enumerates the supported output formats. It is clear what the tool does, though it never contrasts itself with nearby siblings such as inspect_or_create_dxf or run_accoreconsole_script, which could also plausibly produce files.

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?

Usage is only implied by the phrase 'Save or export the active drawing'; there is no statement of when to prefer dwg over pdf/png, no precondition such as an open connection or loaded drawing, and no exclusion pointing away from sibling file-producing tools. The agent must infer the selection criteria from the format list alone.

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