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

Annotations already declare it is a non-read-only, non-idempotent, non-destructive, closed-world write. The description adds genuinely new behavioral facts: the URL is single-use, expires after 24 hours, and is bounded by workspace lifetime. It does not explain what happens on retry or what the returned payload contains.

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?

A single sentence that front-loads the action ('Creates a one-use return URL') and appends the condition and constraints without filler. Every clause carries information.

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-value documentation is not required, and the schema covers all parameters. The description supplies purpose, lifetime, and single-use semantics; the only mild gap is that it never states the prerequisite that the document capability must come from rapier.open, though the schema description covers that.

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%, so the schema already fully documents 'document', 'operation_id', and 'agent'. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy 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?

The description gives a specific verb and resource ('Creates a one-use return URL') plus the triggering condition ('when the person should edit an offline page and send it back'). It is clear what the tool produces, though it never names or contrasts with any sibling tool to disambiguate placement in the document.* family.

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 states a concrete when-to-use condition: the person must edit an offline page and send it back. That is real routing guidance, but no alternatives or exclusions are given (e.g., when to use document.apply_edits or document.save instead of a return URL).

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