Retrieve top posts from any subreddit for a chosen timeframe. Specify subreddit name and time range to get ranked posts, with pagination support for more results.
A subreddit's top posts
| Name | Required | Description | Default |
|---|---|---|---|
| t | No | Timeframe | week |
| name | Yes | Subreddit name (no r/ prefix) | |
| after | No | Pagination cursor from a previous response | |
| limit | No | Items to return, 1-100 |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true covers the safety profile, but the description adds no behavioral context beyond that. It does not mention how 'top' is determined, the default timeframe, pagination behavior, limit handling, or anything about the response, leaving the agent without useful behavioral expectations.
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?
At just five words, the description is short, but it is an under-specified fragment rather than an informative summary. It lacks a sentence structure that could carry a verb, key constraints, or context, making it more under-specification than effective conciseness.
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 and a parameter set that includes an enum, pagination cursor, and limit, the one-line description is insufficient. An agent cannot infer required parameters, defaults, or the shape of the return value, so the description is not complete enough for reliable 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?
The schema provides 100% description coverage for all parameters, including name, t, after, and limit, so the schema already documents their meaning. The tool description itself contributes no additional semantic information beyond what the schema provides, hence the baseline score 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 is a noun phrase ('A subreddit's top posts') rather than a specific verb+resource statement. It identifies the resource and scope, which helps distinguish it from subreddit info or generic post tools, but the missing action verb like 'retrieve' or 'list' makes the intended behavior less explicit.
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 siblings such as get_posts or get_sub_by_name_info. There are no explicit conditions, alternatives, or exclusion criteria for an agent to reason about tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.