Retrieve recent comments by a specified Reddit user, with sort orders for new, top, or controversial and pagination support. Fetch user comment history for analysis or display.
A user's recent comments
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Reddit username | |
| sort | No | Sort order | new |
| 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 readOnlyHint annotation already covers the safety profile. The description adds 'recent' and 'user's' but says nothing about pagination via `after`, sort behavior, default `limit`, or what is actually returned. It does not contradict annotations, but it adds minimal behavioral context beyond them.
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 very short and contains no filler, but it is a sentence fragment rather than a well-structured definition. It is concise at the cost of completeness, and the structure does not front-load critical information beyond the vague resource phrase.
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, the description should clarify return context, but it only says 'comments' without specifying ownership, response shape, or paging behavior. The schema documents inputs, but the surrounding context is too thin for confident invocation alongside similar sibling tools.
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 description coverage is 100%, with all four parameters (`name`, `sort`, `after`, `limit`) already documented. The description adds no new parameter-level semantics beyond implying that `name` identifies the Reddit user whose comments are retrieved, so the baseline score 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 identifies the resource as 'a user's recent comments,' which aligns with the tool name and the required `name` parameter. However, it is a noun phrase without a verb, and it doesn't explicitly state that it fetches comments authored by the user, leaving ambiguity versus sibling tools like `get_comments`.
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?
There is no guidance about when to use this tool versus alternatives such as `get_comments`, `get_user_by_name`, or other sibling tools. No conditions, exclusions, or alternative routing are described, so an agent receives no help selecting the correct tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.