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

The annotations already declare this as a destructive, non-idempotent mutation. The description adds useful behavioral context about legacy status, directory-mode credential restrictions, and first-party OAuth consent for additional memberships, but it does not explain the actual side effect, what membership is changed, or what the result looks like.

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 description is only two sentences and front-loads the legacy endpoint identification before giving constraints. It is dense and jargon-heavy, and the credential-arguments sentence is somewhat disconnected from the empty schema, but there is little wasted text.

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 zero-parameter tool with no output schema, the description gives some important constraints but leaves major gaps: it does not state what room or membership is affected, what the destructive side effect is, or what happens on success. It is partially helpful but not complete enough for confident invocation.

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?

The tool has zero parameters, so there is no parameter semantics burden; baseline 4 applies. The mention of "credential arguments" is slightly confusing because the schema permits no properties at all, but no actual parameter meanings are missing.

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 description identifies this as a "legacy room-enrollment endpoint," which gives a rough sense that it joins or enrolls a room. However, it does not specify what is being joined, whether it adds the caller as a member, or how this differs from nearby tools such as add_room and create_room.

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 provides constraints but no when-to-use guidance. It does not say when an agent should pick join_room rather than add_room, create_room, or other room-related siblings, nor does it explain whether "legacy" means this should generally be avoided.

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