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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the range of results ('broader catalogue', 'more results') and the status filtering capability. It does not disclose details like pagination or time-window behavior, but given annotations cover the operational safety, the description adds moderate value. No contradiction detected.

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 compact (two sentences), conveys purpose, and front-loads the key differentiator before naming the alternative. Every sentence contributes: the first defines scope, the second provides usage guidance. There is no filler or redundant phrasing.

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 read-only list tool with rich annotations (readOnly, openWorld, idempotent) and a fully documented two-parameter schema, the description is largely sufficient. It covers the main decision point (when to use this vs hot_debates). The only minor gap is that it does not explain what 'participation counts' entails or the output format, but the output schema is absent and this is not critical for selection; the tool's usage context is clear.

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 schema already provides descriptions for both parameters (limit and status) with full coverage (100%). The description complements this by explaining that status filtering is a distinguishing feature (differential from hot_debates) and hints at the limit's role in controlling result volume ('more results'). This adds semantic context beyond the schema's straightforward definitions.

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 clear purpose: read the broader debate catalogue and participation counts, with an explicit differentiation from the sibling hot_debates. It mentions status filtering and more results, which helps distinguish the tool's scope. While it doesn't enumerate the exact resource fields, it is specific enough to convey what the tool retrieves.

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 explicitly contrasts this tool with hot_debates: use hot_debates for a quick recent shortlist, use this when needing status filtering or more results. This provides clear guidance on when to choose this tool over its sibling, which is a key part of usage context. The description also implicitly states the value proposition (broader catalogue).

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