reddit-get-postsGet posts from a subreddit.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort: hot, new, top, rising | hot |
| count | No | Number of results to return (default 10) | |
| subreddit | Yes | Subreddit name without r/ prefix | |
| text_only | No | If true, return only id and title per post to save tokens. | |
| time_filter | No | Time filter for top sort: hour, day, week, month, year, all | week |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond the annotations. It does not mention return format, sorting behavior, pagination, or any side effects. Annotations already indicate a safe read-only operation, so there is no contradiction, but the description itself is uninformative.
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 concise sentence that clearly communicates the tool's purpose without any wasted words. It is appropriately sized and front-loaded.
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?
No output schema exists, and the description does not clarify what the response contains or any limitations (e.g., only returns titles, no comments). However, the tool is straightforward and the comprehensive input schema compensates for missing output details, making it adequate for a basic read-only list.
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%, with all five parameters having descriptions. The description does not add any extra semantic detail beyond the schema, so the baseline of 3 is appropriate.
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 'Get' and the resource 'posts from a subreddit'. The 'subreddit' qualifier distinguishes it from sibling tools like reddit-get-post (single post) and reddit-get-user-posts (user 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?
No explicit guidance is provided on when to use this tool versus alternatives such as reddit-get-post or reddit-search. The intended use is implied only by the tool name and description, with no mention of exclusions or prerequisites.
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.