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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are pre-filtered to public, non-demo entries, and the directory is bounded/incomplete so absence of a community is not proof it doesn't exist. It stops short of describing ordering or what happens at the offset ceiling.

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 sentences, zero filler, and the resource definition is front-loaded ahead of the completeness caveat. Nothing is restated from the schema or annotations.

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 two-param paginated read with no output schema and full annotation coverage, this is largely sufficient: it says what comes back (communities and their missions) and warns the listing is incomplete. Minor gap is pagination behavior — ordering and termination — which the agent must infer.

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 0%, so description must carry the burden for limit and offset. 'Read a page' signals pagination semantics but supplies no defaults, bounds (limit max 50, offset max 10000), or guidance on advancing offset — the agent must open the schema to learn any of that.

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?

States a specific verb ('Read a page') and a precisely scoped resource (public, non-demo research communities plus their missions). The resource is clearly distinct from read_public_thread, but the description never clarifies how a 'community' relates to a 'collective' (read_collective), which is the one plausible confusion an agent could have.

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 when-to-use guidance and no alternative named, even though read_collective sits adjacent as a possibly overlapping resource. 'The directory is bounded and may be incomplete' is a data-quality caveat, not usage direction — it does not tell the agent when to reach for this tool or when to stop paginating.

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