save_diagram

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

Annotations already indicate destructive behavior. The description adds the file type context (.drawio/XML) but does not disclose whether existing files are overwritten, what 'regenerate' implies, or side effects of saving. This adds some value beyond annotations but leaves gaps.

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 and is appropriately brief, but it is vague and could include more details without losing conciseness. It does not fully exploit its space.

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?

With an output schema present but no description of it, and only a terse description of the tool's behavior, the agent is left with unanswered questions: what does the output contain, what happens if 'path' is null, and what does 'regenerate' mean? Not complete for a destructive save 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?

Schema description coverage is 0%, and the description provides no explanation of the 'path' or 'diagram' parameters. It only mentions output file formats, which is weak compensation for the lack of parameter documentation.

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 action ('save') and the resource ('diagram'), and specifies the output formats (.drawio or XML). It distinguishes from most siblings by focusing on saving to a file, though it does not explicitly differentiate from 'export_spec'.

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_spec' or 'open_diagram'. The description only states what it does, leaving the agent to infer appropriate usage.

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