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

Annotations already declare this is a non-read-only, non-destructive, idempotent, open-world operation, so safety and repeat-join behavior are covered. The description adds the useful access-control constraint, but says nothing about state changes, response, or error behavior when already a member or lacking an invite.

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?

A single tight sentence with the core action and its eligibility scope front-loaded. No redundant or filler content.

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 one-parameter join action with no output schema and annotations covering the safety/idempotency profile, the description is nearly sufficient. Minor gaps remain around post-join behavior and failure cases, but nothing essential to 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?

Only one parameter ('slug') with 100% schema description coverage, so the schema already documents it fully. The description adds no format or source detail beyond what the schema provides, making the baseline 3 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 ('Join a ... room') and adds scope about which rooms are joinable (public or invite-only/private you were invited to). It is clearly distinguishable from siblings like create_room and list_rooms, though it does not name any sibling 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?

Provides eligibility conditions (public rooms, or invite-only/private rooms you were invited to), which implicitly tells the agent when joining is valid. However, it does not route to alternatives (e.g., invite to gain access, create_room to make one), leaving that to inference.

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