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

Annotations declare destructiveHint=true and idempotentHint=false, but the description frames the operation benignly ('when work should be kept') and never says an existing destination may be overwritten or what is lost. It also omits that re-sending operation_id replays a recorded result — a behavioral trait the schema description, not the tool description, carries.

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 verb is front-loaded in the first clause, but the sentence drifts into obscure phrasing ('hosted door') and the trailing 'The receipt reports verification' is largely redundant given an output schema exists. Not bloated, but not tight or clearly structured either.

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?

Annotations cover the safety profile and the output schema covers the receipt, so much of the burden is carried elsewhere. Still, for a destructive, non-idempotent write, the description leaves the overwrite/loss behavior and any permission requirements unaddressed.

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 100% across all three parameters, so the schema already explains agent, document, and the operation_id retry/replay semantics. The description adds nothing parameter-specific; this is the baseline 3 case where structured data does the lifting.

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?

States a verb (saves/confirms) and a resource (the document), but splits the purpose into two opaque modes — 'the person's chosen local destination' versus 'durable workspace storage on the hosted door' — with 'hosted door' being unexplained jargon. An agent cannot confidently tell which mode applies or how this differs from nearby siblings like document.commit or document.sync.

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 only guidance is the vague clause 'when work should be kept,' which gives no condition an agent can act on. No alternatives are named (commit, sync, create_return are all plausible siblings), no when-not, no prerequisites or auth context.

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