unarchive_document

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

Adds high-impact warning and visibility context beyond annotations. Annotations provide destructive and idempotent hints; description reinforces impact but doesn't cover idempotency or revertibility.

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?

Two concise sentences, front-loaded with the high-impact warning. No extraneous text.

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?

Covers key behavioral impact and user confirmation requirement. Could mention prerequisite (document must be archived) but not essential given simplicity.

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 description repeats the schema's description of 'document_id' without adding additional meaning or usage nuances.

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 clearly states the action: restores an archived document to normal visibility. It distinguishes from sibling 'archive_document' by being its inverse.

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?

Includes explicit warning to confirm with user before invoking, and notes the document becomes visible to all. However, it does not specify when not to use (e.g., if document not archived) or contrast with alternatives.

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