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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: a cost model ('1 credit + 1 credit per subreddit returned') and the pagination contract ('When meta.nextCursor is set, call again with cursor set to it'). It stops short of describing result ordering or what an empty result looks like, but the costly/stateful aspects are disclosed.

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?

Front-loads the purpose, then routes to the alternative, then covers cost and pagination. Every sentence carries information, though the cost and cursor sentences are dense and could be split for scanability.

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?

No output schema exists, so the description carries the return-value burden; it names member counts, `meta.nextCursor`, and the pagination model, which covers what an agent needs to loop correctly. Cost and pagination are covered, but the shape of individual result items is only partially implied.

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 100% so the baseline is 3; the description earns above that by spelling out the concrete pagination loop with `cursor`, which the schema only describes abstractly as opaque and bound to other params. It adds nothing on `sort`, `limit`, or `includeNsfw`, but those are fully documented in the schema.

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 and resource ('Find communities by name or topic') and clarifies the matching surface ('name or description matches') plus what comes back ('member counts'). It separates itself from in-community post search, but never distinguishes itself from the sibling `search_reddit` / `search_subreddit` / `lookup_reddit` tools, so one ambiguity remains.

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?

Gives an explicit use case ('find where a topic is discussed before reading or watching those communities') and names the condition that should route elsewhere ('To search *posts* inside one community, use ... instead'). There is no guidance on when to prefer it over `search_reddit`, but the primary workflow is clear.

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