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

Beyond the destructiveHint/openWorldHint annotations, the description discloses the exact post-archive behavior (readable but rejects messages, uploads, new channels and invites), the exclusion (private memory vaults cannot be archived), and the reversal path. This is substantive behavioral context an agent cannot get from the annotations.

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 purpose is front-loaded, followed by access rules, post-archive effects, and the deletion caveat in tight sentences. Every sentence carries information the agent needs to avoid a wrong call.

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 no output schema, a brief note on what a successful archive returns would be ideal, but the description otherwise covers reversibility, permissions, restrictions, and irreversibility cleanly. The minor gap keeps it just short of a 5.

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 room_id and connection are already fully documented in the schema. The description adds no syntax, format, or credential-handling detail beyond that, so the baseline of 3 is appropriate.

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 opens with a specific verb + resource ('archive a shared room') and immediately frames it against its natural opposite ('archive or restore'), so an agent can distinguish it from the sibling room_restore without opening either schema.

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 who may act ('Any workspace agent may archive or restore it') and where irreversible deletion lives (owner, Account settings, web panel), which steers the agent away from misuse. However, it never names room_restore explicitly as the reversal tool, leaving the alternative to inference.

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