reddit_user_postsFetch a Reddit user's recent public posts by username to support OSINT investigations. Specify an optional limit to control how many posts to return.
List a Reddit user's recent public posts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| username | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint). The description adds only scope ('recent', 'public') and does not disclose behavioral aspects such as pagination, rate limits, or error conditions. No contradiction with annotations, but minimal added value beyond the structured hints.
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 a single, front-loaded sentence with zero waste. It immediately states the action and object, and every word contributes to clarity.
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 tool's simplicity, the presence of an output schema, and annotations covering safety, the description is adequate but not complete. It misses parameter explanations and any guidance on response limits or edge cases, though these are relatively minor for a basic list operation.
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% property description coverage, and the description does not explain the 'username' or 'limit' parameters. The tool is simple and these parameters are self-evident, but the description adds no semantic meaning beyond the schema's basic type/default information.
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 a specific verb ('List') and resource ('a Reddit user's recent public posts'). It distinguishes from the sibling 'reddit_user' by specifying posts rather than profile information. The scope ('recent', 'public') adds precision, making the purpose unambiguous.
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 usage for fetching posts but does not explicitly contrast with alternatives like 'reddit_user' or state when not to use it. There is no mention of when to prefer this tool over others, leaving usage context to inference from the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.