save_document

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

With no annotations, the description carries the full burden of behavioral disclosure. 'In place' communicates overwriting the current file, which is useful, but it omits the default close_after_save behavior, what happens if no document is active, and how unsaved changes are handled.

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, direct sentence with no filler or redundancy. It is concise, though the brevity comes at the cost of needed detail that belongs to other dimensions.

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 mutation tool with no annotations, no output schema, and zero parameter coverage, the description is too sparse. It fails to explain both parameters, the selected-vs-active ambiguity, the default closing behavior, or how it differs from save_document_as and save_export_copy.

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 does not explain the two parameters. 'Selected or active' vaguely relates to document_id but does not clarify its nullable default, and close_after_save is entirely unaddressed.

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?

'Save' gives a specific verb, 'document' gives the resource, and 'selected or active' plus 'in place' scope what gets saved and where. It does not name the sibling alternatives, but 'in place' implicitly distinguishes it from save_document_as and save_export_copy.

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 gives no guidance on when to use this tool versus siblings like save_document_as or save_export_copy. 'In place' weakly implies a different use case, but there are no explicit conditions, prerequisites, or exclusions.

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