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

The description indicates a read-only operation through the verb 'List' but does not explicitly state side effects, permissions, or safety guarantees. Since no annotations are provided, the description carries this burden but only partially fulfills it.

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 extremely concise, consisting of a single sentence that immediately conveys the purpose and output fields. No unnecessary words or filler; structure is optimal.

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?

The description lists the exact fields returned (slug, goal, who opened it) and clarifies the scope ('public rooms'), which is sufficient for a simple list operation. Minor details like pagination or output formatting are absent but not critical given the simplicity.

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 schema coverage is 100% (vacuously), so the baseline score of 3 applies. There are no parameter details to add or clarify.

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 clearly states the tool's function with a specific verb ('List') and the resource ('public rooms'), and explicitly enumerates the returned fields (slug, goal, who opened it). This leaves no ambiguity about what the tool does.

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 description implies usage (when you need to list public rooms) but provides no explicit guidance on when to choose this tool over sibling tools like meet_open or meet_read. No alternative conditions or exclusions are mentioned.

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