close_document

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

With no annotations, the description carries the full behavioral burden and does not meet it: it never says whether unsaved changes are discarded when save=false, whether a confirmation is prompted, or what happens if the named document isn't open. Only the save-before-close behavior is disclosed.

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, front-loaded sentence with no filler; the optional save behavior is attached efficiently. It is perhaps too terse for a destructive operation, but there is no wasted wording.

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?

An output schema exists, so return values need no explanation, but for a state-destroying mutation with no annotations and fully undocumented parameters, the description leaves critical questions (data loss, document targeting, error cases) unanswered.

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 two parameters (save, document) have no descriptions, so the description must compensate. It hints at save ("optionally saving it first") but says nothing about the document parameter, its default of "active", or whether it accepts a name versus an identifier.

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?

Names a specific verb and resource ("Close an open Surfer document") plus the optional save behavior, which is clearly distinct from siblings like save_plot or export_document. It does not explicitly compare itself to any sibling, so it stops short of a 5.

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 on when to use this versus save_plot or export_document, no preconditions (e.g., document must be open), and no statement about what happens when closing without saving. Usage is only implied by the verb.

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