Retrieve hot posts from any subreddit by providing the subreddit name and optional post limit. Get current trending discussions for analysis or display.
Get hot posts from a subreddit.
Args: subreddit: Subreddit name (without r/) limit: Posts to fetch (default: 10)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| subreddit | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool gets hot posts; it does not disclose response shape, pagination behavior, rate limits, or whether any authentication is required. The parameter defaults are repeated from the schema, not added behavioral context.
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 compact and front-loaded with a single-sentence purpose, followed by a structured parameter list. Every line carries necessary information with no redundancy or filler.
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?
The description adequately covers the core action and both parameters, and an output schema exists to explain return values. However, it lacks usage guidance relative to siblings and omits behavioral details like sorting semantics or error cases, leaving gaps for a tool with multiple close alternatives.
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 has 0% description coverage, but the description's Args section adds meaningful semantics: 'Subreddit name (without r/)' clarifies the expected format, and 'Posts to fetch (default: 10)' explains the limit's meaning and default. This compensates for the sparse schema.
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 'Get hot posts from a subreddit' clearly states the verb, resource, and scope. The specific sort order 'hot' and the subreddit-scoped resource distinguish it from sibling tools like reddit_top, reddit_new, reddit_rising, and reddit_front.
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 when to use the tool (when hot posts from a subreddit are needed) but provides no explicit guidance about alternatives or conditions. It does not mention using reddit_front for front-page posts or reddit_top for top-ranked posts, leaving the agent to infer the differentiators from tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.