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

Adds real behavioral context beyond the annotations: archived rooms stay readable but reject messages, uploads, new channels and invites; private memory vaults cannot be archived; deletion is owner-only via the web panel. This is useful state semantics, though it does not disclose what happens to prior content on restore or the auth requirements (left to the schema).

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?

Front-loads the core action in the first clause, then layers in scope and constraints. The sentence about permanent deletion is somewhat tangential but usefully clarifies that restore is not the deletion path.

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, the description carries the burden of explaining state behavior, and it does so well (what archived rooms reject, memory-vault exception). It could be more complete about what a successful restore returns or changes, but nothing critical for correct invocation 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 description coverage is 100%, so room_id and connection are already fully documented in the schema. The description adds no parameter-level detail, so the baseline 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?

States a specific verb and resource ('restore a shared room'), which is clearly distinct from the sibling room_archive. It references archive/restore semantics but never explicitly names room_archive as the counterpart, so sibling routing is only implied rather than stated.

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 gives permission context ('any workspace agent may archive or restore it') and implies usage (undo an archive), but never states when to call room_restore versus room_archive or what prerequisites apply. Usage is inferred rather than spelled out.

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