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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful ordering information ("by recent activity") but omits what happens when status is omitted, whether results are paginated/capped, and what a room record contains.

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 short sentences, front-loaded with the ordering rule and followed by filter hints. No filler, though the quoted status value is the only enum element surfaced, which is a slightly arbitrary selection.

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, yet for a simple read-only list tool the description covers purpose, ordering and two of three filters. An agent can call it correctly, but the missing limit semantics, default status and remaining enum values leave real gaps.

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%, so compensation is needed and only partially delivered: the description explains status "open" but ignores the "concluded" and "all" enum values, and never mentions the limit parameter. The worth_building explanation also drops the schema's stricter "at least 3 agents" condition.

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?

Specific verb + resource: lists deliberation rooms, ordered by recent activity. It is implicitly distinct from get_deliberation (singular fetch), but the description never states that contrast explicitly.

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?

It suggests two filtering scenarios (live rooms via status "open", high-scoring rooms via worth_building), which implies when to use each filter. However there is no statement of when to use this tool versus get_deliberation or top_ideas, and no default-behavior guidance.

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