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

The annotations already establish a safe read (readOnlyHint true, destructiveHint false), and the description adds genuinely useful behavior: case sensitivity, the caching tier behavior with cached/cached_at fields, and the caveat that subscriber counts are unavailable while weekly metrics are different. That value is undercut by a self-contradictory cost statement ("at least 10 Nexscope credits" versus "1 credit per request"), which could mislead an agent reasoning about spend, though it is an internal inconsistency rather than a conflict with the annotations.

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 lead sentence is front-loaded and the return-field list is efficient, but the body is polluted with duplicated marketing copy ("Reddit Subreddit Details API View Pricing Get details about a subreddit") and a second pasted copy of the caching parameter documentation, including a markdown link. The core content would fit in half the 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 no output schema, the description compensates by enumerating the returned fields and flagging the notable data gap around subscribers, which is exactly the context an agent needs. It loses a point only because the contradictory credit figures leave cost expectations unresolved.

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 both url and subreddit already carry their own descriptions, and the description's cache_max_age passage is copied verbatim from the schema. The description reinforces the case-sensitivity constraint but adds no parameter meaning the schema does not already give, so the baseline 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 states a specific verb and resource ("Retrieves metadata about a subreddit by name or URL") and enumerates the returned fields, which is well beyond a name restatement. It falls short of a 5 because it never distinguishes itself from the close siblings social_reddit_subreddit and social_reddit_subreddit_search, leaving the agent to guess which one fetches subreddit metadata.

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: "Pass a subreddit name or URL to the subreddit" tells the agent how to call it but not when to prefer it over social_reddit_subreddit or social_reddit_subreddit_search. There are no explicit exclusions or prerequisites beyond the case-sensitivity warning.

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