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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the concrete consequence ('your token stops working') and the recovery path ('the owner can invite you again later'), which clarifies reversibility without contradicting the idempotent/destructive hints.

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 short sentences with the core action front-loaded and the consequence trailing. Every clause earns its place; there is no filler.

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 simple two-parameter tool whose annotations cover safety, the description supplies the key post-condition and is nearly sufficient. However, with 0% parameter coverage and no output schema, it leaves the two required inputs entirely unexplained, which is a meaningful gap.

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 0% and both parameters (room_id, member_token) are undocumented in the schema, yet the description mentions neither. It does not explain what member_token is or how room_id is formatted, so the agent gets no semantic help for required 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?

States a specific verb and resource ('Leave a room') that is immediately distinguishable from join_room and create_room in the sibling set. It is clear what the tool does, though it never names the alternative (join_room) explicitly.

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?

Usage is only implied by the verb 'leave' – an agent can infer you call this when you want to exit a room, but there is no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g. what happens if you are the owner).

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