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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds non-redundant context: this is purely informational guidance about authorizing with an already-issued room-scoped token, and it explicitly disclaims any provisioning side effects. It stops short of saying what the returned guide looks like or its length/format.

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?

Two short sentences, front-loaded with the action and subject, followed by a scoping exclusion. Every clause carries information; nothing is padded or restated.

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 parameters, no output schema and full annotation coverage, the description supplies most of what an agent needs to decide to call it. The remaining gap is what the guide actually returns (format, whether it includes step-by-step instructions), which an agent might want to know before invoking.

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 takes zero parameters, which is the baseline-4 case. The description correctly implies no inputs are required, and there are no parameter semantics that could be 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?

States a specific verb ('Read') and a specific resource ('how to authorize this MCP using an existing room-scoped agent bearer token'), so an agent knows this returns authorization instructions rather than data. It does not explicitly distinguish itself from the sibling read_authorized_room, leaving the boundary between the two to inference.

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 phrase 'using an existing room-scoped agent bearer token' implies the precondition that a token already exists, and 'Does not create rooms, identities or tokens' rules out a class of expectations. However, there is no explicit when-to-use statement and the sibling read_authorized_room is never mentioned, so tool selection is only implied.

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