Save As

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

Annotations provide only title, so description carries full burden. It details that format derives from extension and how 'format' parameter works, preventing confusion. However, it does not clarify whether the current drawing session now points to the new file (typical Save As behavior), which is a behavioral gap.

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 concise (three short sentences) with purpose front-loaded. Every sentence contributes essential behavior without redundancy.

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 the tool's simplicity and presence of output schema, the description covers format logic well. The only missing element is whether the original drawing is unchanged or the session switches to the new file—a minor gap for such a 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 100%, and the description adds value by explaining the N2 principle (bytes match name) and the override condition in plain language, going beyond schema descriptions. This helps agent understand parameter interplay.

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 saves the current drawing to a new path/format, listing DWG, DXF, or DWT. It distinguishes from sibling tools like 'drawing_save' (which saves to existing path) and 'drawing_export_dxf' (specific export) by focusing on saving to a new location.

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 explains when format override applies, but does not explicitly contrast with export tools or state prerequisites (e.g., ensure drawing is open). The title 'Save As' implies usage for saving copies, but more direct guidance would improve clarity.

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