save_drawing

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, covering the safety profile. The description adds useful behavioral context about in-place versus save-as behavior, but does not disclose what happens if the path already exists (overwrite or fail), which is the main risk for a save operation.

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?

One short sentence, front-loaded with the primary action and qualified by an optional modifier. No filler or 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?

For a one-parameter, zero-required tool with full schema coverage, complete annotations, and an output schema, the description covers what an agent needs. The only meaningful omission is overwrite/confirmation behavior when the target path already exists.

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?

With a single parameter at 100% schema description coverage, the schema already documents 'path' including the .dwg/.dxf extension constraint and the omit-to-save-in-place default. The description only echoes that in prose, so the baseline of 3 applies.

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?

States a specific verb (save) and resource (the active drawing), and the parenthetical clarifies the scope with an optional save-as. It does not explicitly distinguish itself from the closest sibling export_drawing, leaving that inference to the agent.

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 implied rather than stated: 'optionally under a new name' hints at save-in-place vs save-as, but there is no explicit when-to-use guidance or a named alternative to prefer for export/format-conversion scenarios.

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