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

Goes beyond the annotations by warning that `to:"sync"` alone can replace files (consistent with destructiveHint=true), spelling out environment prerequisites for page/docx/pdf on hosted vs self-hosted deployments, and clarifying that export never publishes a website. It adds real operational context, though it says nothing about permissions or what happens to existing files in file mode.

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?

It is dense but not padded, and the dominant `to` modes are front-loaded. The semicolon-chained clause structure and the unusual `to:"file"` notation make it harder to parse than it needs to be.

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 10-parameter, no-output-schema, destructive tool, the description covers delivery modes and environment constraints well but leaves most parameters unexplained. An agent still cannot tell what `document`, `block`, `heading`, `revision`, or `compare_id` expect without guessing.

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 only 10%, so the description must carry the load, and it only explains the `to` and `format` enums. Seven parameters — including the required `document` and the large `text` payload, plus block, heading, revision, compare_id and operation_id — are left entirely undocumented in both schema and description.

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 makes clear this is a delivery/export tool whose behavior is selected by the `to` parameter (file/save/clipboard/sync) and that it produces markdown, html, page, txt, docx, pdf or clipboard-shaped output. The purpose is discernible, but it never states a clean verb+resource sentence and doesn't explicitly contrast itself with siblings like read, show, or edit.

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?

It enumerates what each `to` mode does, which implicitly tells the agent which mode to pick, and notes that hosted Door requires a paired open editor for page/docx/pdf. However, there is no explicit when-to-use-this-vs-alternatives guidance against the sibling tools, and the phrase 'Inspect delivery' is too vague to guide selection.

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