unarchive_document

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

It adds important behavioral context beyond the annotations by warning that this is HIGH-IMPACT, that the document becomes visible to all users, and that confirmation should be requested. This supplements the destructiveHint annotation.

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 sentences with no wasted words. The high-impact warning is front-loaded, followed by the effect and the required confirmation step.

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 single-parameter action tool with no output schema, the description is complete. It explains what happens, why it matters, and what the agent should do before invoking.

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?

The schema description already fully documents document_id as 'The document ID to unarchive' (100% coverage). The description adds no additional parameter-level meaning, so it meets the baseline.

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 states a specific verb ('Restores'), the resource ('previously archived IT Glue document'), and the outcome ('appears in normal views again'). This clearly distinguishes it from archive_document and other document operations.

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 description clearly indicates when to use it: when a previously archived document needs to be restored. It does not explicitly specify when not to use it or name an alternative, but the context is unambiguous.

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