save_document

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention whether saving overwrites an existing file, whether it is destructive, requires specific permissions, or what happens if no path is supplied. This is a significant gap for a mutating 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?

The description is a single, front-loaded sentence with no filler. It communicates the core function and the optional parameter efficiently.

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?

The tool is simple with one optional parameter, and an output schema exists, which likely covers return values. However, the description lacks essential behavioral context—such as overwrite behavior, error conditions, and whether a document must be open—that would make it fully actionable. It is adequate but incomplete for a tool with no annotations.

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 description explicitly explains the 'path' parameter as optional and as a new save destination, adding meaning beyond the schema's bare type definition. With 0% schema coverage, this compensation clarifies the parameter's role, though it omits details like path format or constraints.

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 operation: save the current document, with an optional new path. This distinguishes it from sibling tools like new_document, open_document, close_document, and export_page by naming the specific action and resource.

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 implies the tool is for persisting the current document, but it provides no explicit guidance on when to use it versus alternatives like export_page or close_document. It also omits any prerequisites, such as having an open document, leaving usage context to inference.

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