search_reddit_usersSearch Reddit users by keyword. Returns username, user ID, bio, post and comment karma, account creation date, banner, verified, moderator, employee and NSFW flags and profile link. 25 per page, up to 4 pages. Billed $0.003 per page.
| Name | Required | Description | Default |
|---|---|---|---|
| pages | No | Number of pages to fetch, 1-4 (default: 1). Each page returns up to 25 users | |
| query | Yes | Search keyword (max 500 characters) |
Changes observed during successful MCP inspections.
Input schema / properties / pagesAdded value: +{
+ "default": 1,
+ "description": "Number of pages to fetch, 1-4 (default: 1). Each page returns up to 25 users",
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover the safety profile (readOnly=true, destructive=false, openWorld=true), and the description adds real behavioral context beyond them: pagination limits (25 per page, up to 4 pages) and a cost disclosure ($0.003 per page). These are exactly the non-obvious traits an agent needs, though it stops short of noting rate limits or failure modes.
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?
Purpose is front-loaded, followed by return fields, then pagination and billing in tight sentences with no filler. Slightly dense field enumeration but every sentence earns its place.
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 correctly enumerates the returned fields (username, ID, bio, karma, creation date, flags, profile link), and it adds pagination and cost so the agent can plan a call. Adequate for this read-only search tool.
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%, so both query and pages are already documented, and the description's '25 per page, up to 4 pages' merely restates the pages constraint. Baseline 3 is appropriate since the schema carries parameter meaning.
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?
States a specific verb+resource ('Search Reddit users by keyword') and distinguishes itself from content-search and profile siblings. An agent can tell it apart from search_reddit and reddit_user_profile without opening a schema.
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?
No when-to-use guidance. It never explains when to reach for user search versus search_reddit (content) or reddit_user_profile (fetch a known user), despite many closely related siblings. Usage must be inferred entirely by the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.