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

The annotations only flag destructive=true and openWorld=true; the description earns its keep by saying specifically that sync "can replace files," that page/docx/pdf rendering depends on the deployment, and that delivery should be inspected. That is exactly the kind of beyond-annotation context an agent needs before a destructive call.

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 front-loaded with the use case and then walks modes in a sensible order, with no filler. The mode breakdown is delivered as one long semicolon-chained paragraph with nested parentheticals, which is dense to parse but not padded.

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 destructive, 10-parameter, no-output-schema tool, the description covers mode selection, deployment-dependent rendering, and the replace-files risk. What it omits is the role of the non-mode parameters (revision, compare_id, operation_id, block) and any hint about what a delivery response looks like.

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 coverage is only 10%, so the description has to carry the load. It does well on `to` and maps `format` values onto the two relevant modes (markdown/html/page/txt/docx/pdf vs plain/markdown/formatted/complete), but leaves document, text, block, heading, revision, compare_id, and operation_id entirely unexplained, including the one required parameter.

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 opening clause gives a concrete verb and resource ("their Rapier document as a file to keep") and enumerates the output artifacts, which separates it from read/show/edit siblings. It stops short of naming an alternative tool by name, so the differentiation is by outcome rather than by routing.

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?

Each `to` mode is given an explicit condition: "file" (the default) for a deliverable, "save" for the bound destination, "clipboard" for a passage, and "sync" alone for the Notes store. It also states prerequisites (hosted Door needs the person's paired, open editor) and a clear exclusion ("export never publishes a website"), so the agent knows when not to reach for it.

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