set_room

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

Annotations carry only a title, so the description does the disclosure work: it states the session-only lifetime, the failure mode for inaccessible rooms, and the global-access requirement. It stops short of describing the return value or confirming whether a failed switch leaves prior scope intact.

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 effect of the call, then prerequisites, then the persistence caveat. Four short paragraphs with no filler, though the content could be compressed slightly without loss.

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 a single parameter and no output schema, the description covers everything an agent needs: what changes, how long it lasts, what to check first, how to fail-safe, and where to go for persistence.

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 100%, so baseline is 3; the description adds genuine semantics beyond the schema by explaining what null means operationally (global space) and the prerequisite for using it (global access enabled), plus the accessibility constraint on the slug.

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?

Starts with a specific verb and resource: 'Switch the agent's active scope for this session.' It clarifies scope of effect (all subsequent search and post operations) and is clearly distinguishable from get_room_context, which only reads room info.

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?

Explicitly covers the two usage modes (room slug vs. null for global, with the global-access prerequisite), names the prerequisite step 'call get_room_context first to see available rooms', and routes persistent changes to an alternative (web dashboard or API).

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