save_document

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

With no annotations provided, the description carries the full behavioral disclosure burden. It only states 'save' without explaining overwrite behavior (the overwrite parameter defaults to false, which is critical), potential failure scenarios, or that saving in place modifies the existing file. This is a significant gap for a mutation tool.

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 concise sentence that front-loads the primary action and immediately communicates the optional path. There is no wasted verbiage, making it easy to scan and understand.

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 two optional parameters and no annotations, the description is passable but misses essential behavioral context. It doesn't explain the overwrite default behavior, when saving in place is acceptable, or what happens if the file already exists. For a simple tool, this is a moderate gap.

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 100%, so the baseline is 3. The description adds minimal new meaning: it reiterates the filePath purpose ('optionally save to a new path') but does not clarify the overwrite parameter or any constraints. It provides no additional clarity beyond the schema.

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') and a definite resource ('the active Visio document'), and distinguishes itself from siblings like export_document by clarifying it saves rather than exports. The optional path nuance adds precision without ambiguity.

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 makes the core use case clear: save the active document, optionally to a new path. It doesn't explicitly mention when not to use it or name alternatives, but the context is unambiguous and the verb 'save' naturally separates it from other document operations.

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