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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds domain semantics about grants not changing existing memberships, which is genuinely useful context, but the phrase 'Additional consent creates a separate grant' sits awkwardly against a read-only hint and leaves it unclear whether calling this tool has any side effect at all.

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 with no filler, but the front-loaded sentence does not resolve the add-vs-report ambiguity raised by the tool name. Brevity here comes at the cost of disambiguation rather than being a virtue.

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 zero-parameter read tool with no output schema, the description should at minimum say what information comes back and when it is worth calling. It never describes the return shape, and its only context sentence concerns consent grants, leaving the agent unable to predict the response.

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?

Zero parameters, so the schema has nothing to explain and no compensation is required from the description. Baseline 4 applies.

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 name and title suggest an action (adding/explaining a room), but the description's only concrete claim is that it 'Returns first-party OAuth room-consent information.' An agent cannot tell whether this tool performs an add, explains one, or reports consent state, and nothing distinguishes it from siblings like create_room, join_room, or list_rooms.

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?

There is no when-to-use guidance and no named alternative. The second sentence describes the consequence of 'additional consent' but never says under what circumstances an agent should call this tool instead of create_room, join_room, or room_situation.

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