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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds meaningful auth context (members key vs a purchased reader pass), but says nothing about pagination, feed contents, or return behavior.

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 sentences, purpose front-loaded, no wasted clauses. The embedded reader-pass URL is dense but adds actionable detail rather than filler.

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?

There is no output schema, so the description carries the return-value burden, yet it never describes what a feed or room list contains, nor the effect of 'limit'. Adequate on access modes, incomplete on what comes back.

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 only 33% and the description must compensate, but it only clarifies 'key' (members room key) and the reader-pass mode. The 'room' and 'limit' parameters remain undocumented in both the schema and the description, leaving a real gap.

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 resource (collaborative rooms) and two clear operations: listing public rooms or reading one room's feed. An agent can tell this is the read side of the room feature. It does not explicitly contrast with the likely write sibling post_to_room, so it falls short of full sibling differentiation.

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?

Explains the two access paths – a room key for members or a reader pass – which implies when to use each. However it gives no when-not guidance and never points away from alternatives like post_to_room for writing, leaving routing to inference.

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