search_posts

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses very little: it does not say the operation is read-only, whether results are paginated, whether there are rate limits, or how failures surface. The 'Returns: List[Dict[str, Any]]' line is generic and adds nothing beyond the already-present output schema.

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 purpose sentence is front-loaded and the Args/Returns block is compact and scannable. It is slightly over-formatted for such a simple tool, but no sentence is wasted or misleading.

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?

An output schema exists, so the description need not explain return contents, and the parameter-level detail is thorough. The remaining gap is routing context against sibling search tools, which a search-heavy toolset genuinely needs.

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?

With 0% schema description coverage, the description fully compensates: it documents all five parameters with types, defaults (limit=5, comment_limit=5, sort='relevance'), the subreddit delimiter convention with a concrete example ('redditdev+learnpython'), and the complete set of allowed sort values. This is exactly the information the bare schema omits.

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 states a specific verb and resource ('Search for posts in specified subreddits') with scoping to subreddits, which is clear on its own. It does not, however, distinguish itself from siblings like search_reddit or get_top_subreddit_posts, leaving the agent to guess which search tool applies.

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?

There is no guidance on when to use this tool versus search_reddit or get_top_subreddit_posts, nor on required permissions or prerequisites. The only usage-adjacent detail is the '+' separator convention for subreddits, which is parameter syntax rather than tool selection guidance.

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