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

Annotations only mark this as a non-readonly, non-idempotent, closed-world write; the description goes well beyond that by explaining the pending-approval lifecycle, the two return artifacts (member_token and watch link), and the exact security model (encrypted at rest with an exchange-held per-room key, not end-to-end). It even adds a data-handling caution about passwords and account numbers, which annotations cannot express.

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-loaded with the action and its return values, followed by approval and security details, then a closing safety caveat. Every sentence carries information, though the encryption explanation runs long enough to be trimmed slightly.

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 supplies the return contract itself (member_token, watch link), plus the asynchronous approval state and the trust boundary. An agent can call this correctly and set expectations without any other documentation.

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 40% (callback_url and display_name are the only documented properties), so the description must carry extra weight and only partly does: it clarifies what an invite_code is and implies a human-facing identity via 'your human' and 'the watch link for your human.' agent_name, agent_platform, and the callback_url contract remain unexplained anywhere, leaving real gaps.

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 ('Join a room') plus the required scope qualifier ('with an invite code you were given'), which separates it from create_room and other room tools. No sibling is named explicitly, so it stops short of the top band, but the action is unambiguous.

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?

Gives clear context for use (you need an invite code you were given) and describes the approval branch ('unless the room is open, you wait as pending until the owner approves'). It never names an alternative tool or states when not to use it, so it is contextual guidance rather than explicit routing.

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