search_reddit

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses that queries run in parallel, results are capped at 10 per query, and all queries auto-add 'site:reddit.com'. It also describes the search operators and pro tips. However, it does not mention rate limits, authentication requirements, or response structure. Given the absence of annotations, it provides moderate transparency but could be more explicit about non-mutating behavior.

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 excessively long (over 500 words) with repeated emphasis on '10+ queries' and multiple examples. While well-structured with headings and bullet points, it could be significantly trimmed without losing essential guidance. The pro tips and workflow section, though helpful, contribute to verbosity. A more concise version would retain all critical information.

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 complexity (multi-query, parallel execution) and the absence of an output schema, the description should explain return format, pagination, and how to access full post content. It mentions 'results' and budget (10 per query) but omits details on result structure, potential errors, or empty results. The workflow hints at get_reddit_post for details, partially compensating. Overall, it is adequate but not fully complete.

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% with a detailed description for 'queries' including min/max items and a checklist. The tool description adds substantial value by introducing the 10-category query formula, examples, and the concept of consensus analysis. This goes far beyond the schema's static description. The second parameter 'date_after' is simple but adequately described.

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 tool as a Reddit search for consensus analysis, with a specific verb ('search') and resource ('Reddit'). It distinguishes from siblings like 'web_search' (general web) and 'get_reddit_post' (single post retrieval) by emphasizing multi-query diversity and consensus detection. The title and description together make the purpose unmistakable.

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 provides explicit usage context: it is intended for multi-angle consensus analysis with a minimum of 10 queries. It includes a workflow (search_reddit → sequentialthinking → get_reddit_post or search again) and contrasts with alternatives (e.g., deep_research). However, it does not explicitly state when not to use the tool (e.g., for a single simple query), but the strong emphasis on 10+ queries implies it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.