reddit-searchSearch Reddit for posts matching a query.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order: relevance, hot, top, new, comments | |
| count | No | Number of results to return (default 10) | |
| query | Yes | Search query string | |
| subreddit | No | Limit search to a specific subreddit | |
| text_only | No | If true, return only id and title per post to save tokens. | |
| time_filter | No | Time filter: hour, day, week, month, year, all |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint, idempotentHint, and destructiveHint, but the description adds no extra behavioral context such as pagination, rate limits, or return format. The description is essentially a restatement of the title with no additional operational details.
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 a single, front-loaded sentence with no fluff. It earns its place but is extremely brief, lacking any additional structure or guidance that could aid the agent.
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?
There is no output schema, so the description should explain what results look like, but it only states that it returns posts matching a query. It does not mention default sort/time filter behavior or result fields, leaving the agent to infer from parameter descriptions and annotations.
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?
All 6 parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description does not add any parameter-specific information beyond what the schema already provides.
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 'search' and the resource 'Reddit posts matching a query', which distinguishes it from sibling tools like reddit-get-post and reddit-get-posts that fetch specific posts. It provides a specific action and target, making the tool's purpose unambiguous.
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 when a keyword-based search is needed, but it does not explicitly mention when to use this tool versus alternatives like reddit-get-posts. There is no exclusion or alternative guidance, though the verb 'search' offers some implicit context.
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.
Each tool is uniquely distinguished by platform prefix (reddit vs twitter) and specific action (get a post, get posts, search, etc.). No two tools have overlapping purposes, even within the same platform.
Tool names consistently use lowercase with underscores and a platform prefix, but the pattern is slightly mixed: Reddit tools use 'get' and 'search' as verbs, while Twitter tools include nouns like 'news', 'thread', and 'user-tweets' alongside verbs. Still, names are predictable and readable.
With 10 tools covering two major social platforms, the count is well-scoped. Each tool serves a distinct, meaningful purpose, and no tool feels redundant or unnecessary.
The tool set provides strong read coverage for both Reddit and Twitter, including search, post/thread retrieval, and user timelines. However, it lacks any write or interaction capabilities (e.g., posting, commenting, liking), which is a notable gap for a social media server and could limit agent workflows.