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

The readOnlyHint annotation already establishes the safety profile. The description adds minimal behavioral context by revealing the return content includes activity counts, but it does not explain ordering, scope, or what 'activity counts' represents. No contradiction with the annotation.

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?

The description is a single terse phrase with no wasted words. It is front-loaded and appropriately sized, though a full sentence with an explicit verb would marginally improve it.

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 parameterless, read-only list operation with no output schema, the description plus annotation covers the essentials: what it returns (topic chat rooms, activity counts) and that it is safe to invoke. Minor ambiguity remains about whether all rooms or only subscribed ones are returned, but the simplicity of the tool keeps this gap small.

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 has zero parameters and the schema is empty with 100% coverage. Per the baseline for 0-param tools, the description need not compensate for parameter documentation, and it appropriately remains silent.

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 title supplies the verb ('List') and the description specifies the resource ('topic chat rooms') plus what is included ('activity counts'). This is clear enough to distinguish from read_room, which targets a single room, though it does not explicitly name any sibling.

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?

No guidance is given about when to use this tool versus alternatives like read_room or list_open_questions. There are no conditions, exclusions, or mention of a follow-up read workflow, so the agent must infer usage entirely from the resource name.

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