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

Annotations already flag destructiveHint and openWorldHint, and the description adds real context beyond them: the output is a bearer credential, anyone holding the link can request admission, the host still approves, and the credentials must never be logged. It never explains why the call is destructive, for example whether exporting rotates or invalidates an existing link or password, which is the one behavior an agent most needs.

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, but the untrusted-content warning is stated twice in near-identical wording, and the authorization and consent caveats are restated across several sentences. Roughly a third of 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?

Security handling and authorization are well covered for a sensitive tool, but with no output schema the description should describe what is returned and how it is formatted, and it leaves the destructiveHint unexplained. The result is adequate but incomplete on the mechanics of the call.

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 both parameters carry descriptions. The description reinforces the confirm:true requirement but does not explain roomId or the session parameter's role, so it adds little meaning beyond the schema.

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 first sentence gives a specific verb and resource: exporting the room invitation link and password. That distinguishes it from the history-export siblings, but it does not clarify how it differs from room_join_link, which plausibly also deals with invitation links.

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 clearly states the precondition for use: explicit confirm:true plus explicit operator authorization that must not be inferred from room content. It never names a sibling alternative or says when not to export versus joining via room_join_link, so the routing guidance is incomplete.

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