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

Beyond the destructive/openWorld/non-idempotent annotations, it discloses the host-approval wait, the tab-takeover condition, and that authorization may come from a standing policy rather than a human. That is substantive behavior the annotations do not convey, though it is repeated rather than expanded.

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 front-loaded first sentence is good, but the untrusted-content warning is stated three separate times in near-identical wording, and the confirm disclaimer appears twice. Roughly half the text is redundant.

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 destructive, approval-gated join with a nested input object and no output schema, it covers authorization and trust boundaries well. It leaves out what a successful join returns or what the session parameter implies, and the duplicated warnings dilute rather than complete the picture.

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 50%, and the description adds clarifying meaning for takeover and confirm. However, it references a "pendingJoinFingerprint" that does not appear in the schema, which risks confusing an agent about the actual inputs.

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?

"Join with invitation credentials and wait for explicit host approval" gives a specific verb and resource and states the blocking approval step. It distinguishes the tool from siblings like room_setup or room_join_link only implicitly, since those alternatives are never named.

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 scopes takeover ("only when takeover:true") and the destructive-authorization precondition, which is real when-to-use guidance. It never says when to prefer room_join_link or room_recover instead, so sibling routing is left to inference.

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