reddit_subreddit_about

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

With no annotations, the description carries the full burden. It discloses that data is RSS-derived, and that subscriber counts/icons/banners are omitted because Reddit's no-auth about JSON is unreachable. This is good transparency about limitations, though it doesn't cover rate limits or authentication (implied none needed).

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 description is two sentences with no wasted words. First sentence clearly states the purpose; second adds important caveat about omitted data. Information is front-loaded and to the point.

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?

The description says 'returns RSS-derived public metadata and sample posts' but does not detail the return structure. Since there is no output schema, more specificity on what fields are included would improve completeness. The caveat about omissions adds some context but overall the return format is vague.

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% (both 'limit' and 'subreddit' are described in the schema). The description adds minimal extra info: subreddit should be without 'r/' and limit defaults to 25, clamps to 100. But schema already includes these details, so description adds little value beyond baseline.

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 description clearly states the tool retrieves Reddit subreddit metadata, specifying it returns RSS-derived public metadata and sample posts. It also notes what is omitted (subscriber counts, icons, banners) and why, distinguishing it from sibling tools like 'reddit_subreddit_posts' or 'reddit_subreddit_comments'.

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?

The description implies usage for obtaining metadata and sample posts, but does not explicitly state when to use this tool versus alternatives (e.g., reddit_subreddit_posts for posts, reddit_subreddit_comments for comments). No when-not or alternative tools are mentioned, leaving some ambiguity.

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