save_drawing

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

The description only says 'Save' with no elaboration on behavioral traits such as file overwriting behavior, default filename handling, or whether the action is destructive. Since there are no annotations, the description should have provided more context.

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 a single sentence with no fluff. However, it is overly brief for the tool's importance, sacrificing needed detail for brevity.

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 presence of an output schema (context signal) and only one optional parameter, the description should have covered return value expectations and default behavior. It is incomplete for a write operation.

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?

The input schema has 1 parameter 'filename' with 0% description coverage. The description adds 'as DXF' but does not explain the parameter's meaning, default behavior (null implies auto-naming?), or any constraints on the filename.

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 verb 'Save' and the resource 'current drawing' with the specific format 'DXF'. It distinguishes from sibling tools like export_model and save_openscad which target other formats.

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 versus alternatives like export_model or save_openscad. There is no mention of prerequisites or scenarios where this tool is preferred.

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