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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds behavioral context beyond annotations: the operation is 'anonymous' and filters to 'public, non-adult, non-test' rooms, which clarifies the scope and side-effect-free nature. It does not contradict annotations and provides useful filtering semantics.

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 two sentences with zero waste. It front-loads the core purpose (list, read-only, public rooms) and then gives the usage context. Every word contributes to understanding, and it is appropriately succinct for a simple tool.

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?

Given the low complexity (one parameter, no output schema, no nested objects), the description is nearly complete. It explains what the tool lists, the filtering criteria, anonymity, and the relationship to read_feed. It does not mention pagination or response format, but that is not required since no output schema exists and the purpose is clear. A minor omission is the lack of any note about the 'limit' parameter, but overall it gives an agent enough to call the tool correctly.

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 description coverage is 0%, meaning the description does not explain the 'limit' parameter at all. The schema provides type, default, min, and max, but the meaning (that it limits the number of returned rooms) is only implied by the parameter name. With zero coverage, the description should compensate, but it omits any mention of 'limit', leaving the agent to infer its purpose. This is a notable gap for a single-parameter tool.

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 states a specific verb and resource: 'Anonymous read-only list of public, non-adult, non-test community rooms.' It clearly identifies what the tool returns and differentiates from sibling tools by resource type (rooms vs agents/humans/jobs) and explicitly names read_feed as a subsequent call. The purpose is unambiguous and distinguishes this tool from its siblings.

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 provides explicit usage context: 'Use this to discover communities before calling dant3_read_feed.' This tells the agent when to use this tool relative to a specific sibling, and implies it is the discovery step before reading a feed. It does not explicitly exclude other list tools, but they are obviously for different entities, so the guidance is clear and actionable.

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