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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the sentence 'Read-only: returns public data and changes nothing' largely duplicates structured metadata. The one genuinely additive fact is the credit cost ('Costs 1 credit per request'), which is not expressible in annotations, but nothing is said about result limits, ranking, or pagination behavior.

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?

Three short sentences, front-loaded with purpose and then behavior and cost, with no filler. The opening sentence is redundant with the title rather than wasteful in length.

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?

With a 100%-documented schema and annotations covering the safety profile, the description is complete enough for an agent to call the tool correctly. It lacks any note about the cursor-based pagination flow or what a community result contains, but no output schema exists to lean on, leaving a modest gap.

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 100%, so all five parameters, including the sort/time enums and the cursor, are already documented in the schema, which sets the baseline at 3. The description contributes no additional meaning about how query text is matched or how relevance sorting works.

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 sentence 'Search Reddit communities' gives a verb and a resource but is effectively a restatement of the title, so it adds little. It never clarifies that 'communities' means subreddits, nor distinguishes itself from reddit_search_all, reddit_search_posts, or reddit_search_users, which sit right beside it in the sibling list.

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 or when-not-to-use guidance and no named alternative. An agent must infer on its own that reddit_search_all is the broader tool and that reddit_search_posts searches content rather than communities.

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