reddit_subreddits_posts

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

With no annotations, the description carries the full burden. It discloses that posts are 'normalized public posts' and provides specific handling for 503 throttling responses, which is useful. However, it does not mention read-only nature, authentication requirements, pagination behavior, or return format details, leaving gaps in behavioral transparency.

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 three sentences, front-loaded with the core purpose. Each sentence adds value: first states the action, second clarifies return characteristics (normalized, public), third provides actionable retry guidance. The slight repetition of 'multi-subreddit' does not detract from overall efficiency.

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?

This is a moderately complex tool (5 params, no output schema, no annotations). The description covers purpose and error handling but does not explain return values in detail (e.g., fields, structure) or default behaviors for sort/time/limit, which the schema does not cover. It is adequate but not comprehensive.

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 the schema already documents all 5 parameters. The description adds minimal parameter-related meaning beyond the schema, only indirectly hinting at the 'subreddits' parameter via 'multi-subreddit'. This aligns with the baseline of 3 for high schema coverage.

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 the tool's action ('List') and resource ('Reddit multi-subreddit posts') and provides an additional clarifying sentence about returning normalized public posts from a combined multi-subreddit feed. This distinguishes it from single-subreddit tools like reddit_subreddit_posts by explicitly emphasizing the multi-subreddit scope.

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 the tool is for fetching posts across multiple subreddits ('combined multi-subreddit feed') but does not explicitly state when to use it over alternatives, nor does it mention exclusions or prerequisites. The 503 retry note is operational guidance, not usage selection guidance.

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