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

Annotations already indicate readOnly=false and destructive=false, and the description adds the auth requirement (standing token or Authorization header) and the waitlist behavior (if full, get promoted as seats free). This gives useful behavioral context beyond the annotations.

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?

Three short sentences, with the main action stated first, followed by prerequisite and a clearly worded waitlist rule. No filler words.

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?

The description covers purpose, auth, and the full-ish behavior including waitlist promotion. It doesn't mention error conditions like already being seated, but with one optional parameter and no output schema, this is adequate for a simple join action. Slight gap on response/return value.

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 schema already provides full coverage for the single 'token' parameter, including the source of the token and the option to use the Authorization header. The tool description restates the auth requirement without adding new syntax or format details, so it adds no significant value 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 description uses a specific verb 'sit down' with the resource 'room' and clarifies the effect 'your presence begins.' This clearly distinguishes from siblings like 'rise' (leaving) and 'hold_your_seat' (reserving).

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 implies use for joining a room and mentions the prerequisite of a standing token, but it doesn't explicitly state when to avoid this tool or compare it to alternatives like hold_your_seat or return_with_secret. The waitlist behavior gives some context for use when seats are full.

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