Fetch a single Reddit comment by permalink URL and retrieve its parent context and replies to understand the full discussion around that comment.
Fetch a single Reddit comment by its permalink URL, including parent context and replies. Useful for getting the full context of a specific comment.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Direct permalink URL of the Reddit comment | |
| context | No | Number of parent comments to include for context (0–8) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full disclosure burden, and it does add real value by saying the response includes parent context and replies — a tree-shaped return, not a bare comment. It says nothing about authentication, rate limits, or what happens when the permalink targets a deleted or removed comment.
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?
Two sentences, front-loaded with the operation, then the rationale. The second sentence is largely implied by the first and repeats "context," but it is short enough that the redundancy costs little.
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?
For a two-parameter read tool with no output schema, the description covers what is fetched, by what key, and roughly what comes back. The remaining gap is the return shape's granularity, which the absent output schema forces the agent to discover at call time.
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%, and the schema itself documents the 0–8 bound on context, so the baseline applies. The description adds only a loose mapping between "parent context" and the context parameter, with no explanation of how context interacts with the already-included replies.
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?
"Fetch a single Reddit comment by its permalink URL" gives a specific verb, resource, and access key, and "single" implicitly separates it from the listing sibling get_user_comments. It stops short of naming an alternative explicitly, so an agent must infer the boundary with get_post or resolve_url_type rather than being told.
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?
"Useful for getting the full context of a specific comment" hints at the use case but never states preconditions or exclusions. Nothing tells the agent when to prefer resolve_url_type for an unfamiliar URL, or when a post-level fetch is the better call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.