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

The description adds substantial behavior beyond the annotations: the document reopens fresh and its prior share links, favourites and Recent entries are permanently gone. However, that disclosure of lost metadata conflicts with destructiveHint=false, which promises only additive changes, so the agent gets contradictory safety signals. The description is more informative than the annotation here, but the mismatch is a real defect.

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?

Three short sentences, front-loaded with the action and destination, then the consequence, then the discovery hint. Occasional editorial phrasing ("It opens again, starting fresh") and awkward punctuation cost a point but nothing is 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?

With an output schema present, 3 fully documented parameters, and only a simple move operation to describe, the description covers destination semantics, the default case, and the irreversible side effects. Only the sibling disambiguation against restore_document is missing.

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 100% and the schema already documents teamId, folderId, documentId, and the destination default. The description restates the destination options but adds no new syntax, format, or constraint beyond what the structured schema provides, so the baseline 3 applies.

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 ("Move an archived document back") plus the exact destinations (personal library top, a folder, or a team). It is clear on its own, but it never contrasts itself with the sibling restore_document, which an agent must disambiguate from unarchive_document.

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 supplies an explicit discovery path ("find_documents with archived true lists the archived documents") and states the destination default when neither folderId nor teamId is given. It stops short of saying when this is preferable to restore_document or delete/archive, so it is clear context without full exclusions.

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