Scrape a subreddit in bulk

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

No annotations are present, so the description must disclose behavior. It mentions 'bulk' and 'far more than a single listing page' but does not explain the output format, pagination, rate limits, or potential side effects. The absence of an output schema makes this a significant gap.

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 concise and front-loaded with the primary action, followed by usage context in a few sentences. It avoids fluff but could benefit from a structured breakdown of parameters.

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 no output schema and no annotations, the description omits crucial details such as the return format, pagination behavior, error conditions, and how the tool handles large bulk requests. An agent would lack information needed to correctly interpret the response or anticipate failures.

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?

The description adds meaning to the date window and comment inclusion, but leaves maxPosts, includeNsfw, and other parameters implicit. With only 29% schema coverage, the description partially compensates but does not fully explain the relationship between maxPosts and maxCommentsPerPost or the semantics of includeNsfw.

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 action (pull posts in bulk) and the resource (subreddits), and distinguishes from URL-based scraping with 'Subreddit names only, not post links.' It does not explicitly name sibling tools, but the intent is unambiguous.

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 use cases: building a dataset, trend analysis, or 'what has r/X been discussing since <date>'. It also sets a boundary by noting it accepts subreddit names only, not post links. However, it does not directly contrast with search_reddit or scrape_reddit_urls.

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