Get posts from a subreddit. Returns titles, scores, comments. Args: subreddit: Subreddit name (e.g. 'technology') sort: Sort order: 'hot', 'new', 'top' (default 'hot') max_results: Max posts (default 25)
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | hot | |
| subreddit | Yes | ||
| max_results | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds value by stating what is returned (titles, scores, comments) and detailing sort options and defaults. This provides behavioral context beyond the structured fields, though it doesn't disclose potential errors or limits.
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 compact and front-loaded: one purpose sentence followed by a clear argument list. Every sentence is informative and there is no redundancy, making it easy for an agent to parse quickly.
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 explicitly states the return fields (titles, scores, comments) and documents all parameters. It does not cover error cases or rate limits, but for a simple read-only tool this is sufficient and complete enough for invocation.
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 0%, so the description carries full responsibility for parameter meaning. It does this well: it gives an example for subreddit, lists valid sort values ('hot', 'new', 'top'), and specifies defaults for both sort and max_results, adding significant meaning beyond the raw schema.
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 verb and resource: 'Get posts from a subreddit' and even lists the return fields (titles, scores, comments). While it does not explicitly differentiate from sibling tool search_reddit, the purpose is specific enough to be understood.
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 use case is implied: fetching posts from a specific subreddit. However, there is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling search_reddit as an alternative, leaving the decision to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The two tools have distinct purposes: get_subreddit browses a subreddit's posts by sort order, while search_reddit queries for posts by search terms. Though both return posts, the presence of a required query in search_reddit clearly separates their functionality.
Names follow a verb_noun pattern (get_subreddit, search_reddit) and are lowercase with underscores. However, get_subreddit is slightly misleading because it actually retrieves posts from a subreddit, not the subreddit itself, which creates minor ambiguity.
With only 2 tools, the server feels thin, but it is borderline for a narrow use case of simply reading Reddit posts. The scope is limited enough that 2 tools could be acceptable, though most servers would benefit from additional capabilities.
The server only supports reading posts via subreddit browsing and search. It lacks comment retrieval, posting, voting, user info, and other standard Reddit operations, which are significant gaps for a server named 'reddit-mcp-server'.