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

Annotations already declare readOnly and openWorld, and the description still adds real context: the Atom-feed fallback case where scores and comment counts are null, the meaning of raw.via, extra raw.posts fields, and a 1-credit cost. This is beyond what the annotations provide and useful for interpreting degraded responses.

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?

Four compact sentences, topic front-loaded, no filler. The 'raw.posts' and 'raw.via' fragments are terse to the point of ambiguity since neither appears as a parameter in the schema, but overall it is tight.

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, no-output-schema tool, the description covers what comes back, the sort/timeframe relationship, the degraded Atom case and credit cost. Missing only pagination behavior and any sibling routing, which keeps it short of full coverage.

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?

With 67% schema coverage, the schema already documents limit, cursor, subreddit and timeframe. The description reinforces the sort/timeframe coupling (top and controversial accept a timeframe) but does not add syntax or defaults, and cache_max_age is undocumented in both places.

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+resource: posts from a subreddit, with sort order, scores and comment counts. It is clear what the tool returns, though it never names siblings like reddit_search or reddit_userPosts to disambiguate when this endpoint rather than those applies.

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 at all. An agent choosing between reddit_subreddit, reddit_search, reddit_subredditDetails and reddit_userPosts gets no routing help; the description only documents behavior of the call once made.

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