Search Reddit posts. Returns titles, scores, comments, and content. Args: query: Search query (e.g. 'best programming language') subreddit: Specific subreddit (optional, e.g. 'programming') max_results: Max posts (default 20)
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| subreddit | No | ||
| max_results | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds useful behavioral context by specifying the return content (titles, scores, comments, content) and the default max_results. However, it does not disclose rate limits, sorting behavior, or potential limitations.
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 concise, with a clear opening sentence and a structured parameter list. Every element provides value, and the format is easy to scan.
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 search tool with 3 parameters, the description covers the essential inputs and outputs. It lacks details about result ordering or result count limits beyond the default, but these are not critical given the straightforward nature of the tool and the presence of an output-free schema.
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 fully compensates by explaining each parameter with examples: query ('best programming language'), subreddit ('programming'), and max_results (default 20). This goes well beyond the bare schema definitions.
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's function: 'Search Reddit posts' and what it returns ('titles, scores, comments, and content'). This distinguishes it from the sibling tool 'get_subreddit', which presumably retrieves subreddit metadata rather than searching posts.
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 through the optional 'subreddit' parameter and provides concrete query examples, but it does not explicitly state when to use this tool versus the sibling 'get_subreddit' tool. There is no exclusion or alternative guidance.
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'.