Fetch posts from a specified subreddit with configurable sorting, time range, pagination, and result limits.
Fetch posts from a subreddit
| Name | Required | Description | Default |
|---|---|---|---|
| t | No | Timeframe for sort=top/controversial | |
| sort | No | Sort tab | new |
| after | No | Pagination cursor from a previous response | |
| limit | No | Items to return, 1-100 | |
| subreddit | Yes | Subreddit name (no r/ prefix) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, and the description simply repeats the read-only nature with 'Fetch' without adding extra behavioral context. It does not mention pagination, default limit, sort-specific behavior, or any other runtime characteristics beyond what the schema already states.
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?
A single sentence with no filler, direct and front-loaded. It communicates the essential purpose without redundancy.
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?
Given the lack of an output schema and the presence of many overlapping sibling tools, the description is too sparse. It does not clarify how get_posts relates to get_sub_by_name_top, get_sub_by_name_info, or get_search, nor does it mention that the response is a post listing. The schema covers parameters well, but tool selection context is incomplete.
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%, so the baseline is 3. The description adds no parameter meaning, but also needs none because every parameter already has a descriptive schema entry.
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 'Fetch' and the resource 'posts from a subreddit', making the core function obvious. It distinguishes itself from get_comments and get_post_by_id, but does not differentiate from similar subreddit-listing siblings like get_sub_by_name_top or get_search.
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 provides no guidance on when to use this tool versus its many siblings. It does not mention alternatives, exclusions, or typical use cases, leaving the agent to infer selection solely from the tool name and generic description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.