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

Beyond the readOnly/openWorld annotations, the description discloses credit cost, cache-vs-live behavior (0 credits cached, 1 credit live), pagination via `after`, and a trimmed response mode — genuinely useful operational context. It is undercut by an internal inconsistency ("at least 10 Nexscope credits" in one place, "1 credit per request" in the pasted pricing blurb), which muddies the cost model.

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 core is front-loaded and efficient, but the text is padded with a pasted marketing fragment ("Reddit Subreddit Posts API View Pricing Get recent posts from a subreddit with engagement metrics 1 credit per request") and a verbatim duplicate of the cache_max_age parameter documentation. Those sentences do not earn their place.

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 no output schema, the description usefully compensates by listing the returned post fields, and it covers cost and caching. It still omits page size / how many posts per call and how pagination terminates, and the conflicting credit figures leave the cost picture ambiguous.

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 every parameter is already documented, and the description mostly restates it (sort values, timeframe, after, trim). It adds only marginal meaning beyond the schema, so the baseline of 3 applies.

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 opening sentence names a specific verb and resource ("Fetches posts from a subreddit with sorting and filtering options") and enumerates the returned fields, so an agent knows exactly what it retrieves. It does not, however, distinguish itself from close siblings such as social_reddit_subreddit_search or social_reddit_subreddit_details, leaving that differentiation to the name alone.

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?

Usage is only implied: the required `subreddit` parameter and the `after` token hint at "given a known subreddit, list its posts." There is no statement of when to prefer this over social_reddit_search or social_reddit_subreddit_search, and no prerequisites or exclusions are given.

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