Check any Reddit account's visibility, age, karma, and recent post removals to avoid posting from shadowbanned or suspended accounts.
Check a Reddit account before posting: whether other people can see it (not shadowbanned or suspended), its age and karma, and its recent posts with any removals.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes |
Changes observed during successful MCP inspections.
v0.2.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It states it checks visibility, age, karma, and recent posts but does not disclose potential limitations (e.g., whether it handles private accounts, rate limits, or how recent 'recent' is) or the exact output format. This is acceptable but shallow.
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, concise sentence that front-loads the purpose and then details what is checked. It wastes no words and is easy to scan.
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 relatively simple tool with one parameter and no output schema, the description is fairly complete for basic usage. However, it lacks information on return format, error conditions (e.g., nonexistent username), or how this integrates with the posting workflow beyond 'before posting'.
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 0%, so the description must compensate for the single 'username' parameter. The description implies the username identifies the account but does not specify format, validity, or examples. Baseline for few parameters is moderate; it adds no meaningful detail beyond the 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 clearly identifies the purpose: checking a Reddit account before posting, including visibility status, age/karma, and recent posts with removals. It distinguishes this from posting or community-finding tools, though it doesn't explicitly differentiate from siblings beyond context.
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 before posting ('before posting') and specifies what it checks, but it does not explicitly state when not to use it or name alternatives. With siblings like 'post_status' and 'threadfox_full_kit', additional guidance on when to choose this tool over them would be beneficial.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.