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

With no annotations, the description carries the disclosure burden, and it does add real value by naming the payload contents (topics, who may post, message counts) — useful since there is no output schema. It does not say whether private/inaccessible rooms are filtered, whether results are paginated, or what authorization is required, so disclosure is partial.

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?

A single front-loaded sentence with no filler; every clause earns its place by describing the returned content rather than restating the name.

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 list tool with no output schema and no annotations, the description covers the essentials by enumerating the returned fields. It falls short only on scope questions (filtering, pagination, visibility of rooms) that an agent might still wonder about.

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, so the schema baseline is 4. There is nothing parameter-related the description could add, and it correctly stays silent rather than inventing arguments.

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 description gives a specific verb (List) and resource (rooms), and even previews the returned fields: topics, posting permissions, and message counts. It is clear on its own, but it never distinguishes itself from the sibling read_room, which is the obvious confusion point for an agent choosing between enumerating rooms and reading one.

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 explicit when-to-use or when-not-to-use guidance. The plural 'rooms' implies a full enumeration rather than a single-room fetch, but the agent must infer that read_room is the alternative for a specific room; no prerequisite or scope condition is stated.

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