Scrape Reddit URLs

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

With no annotations at all, the description carries the full disclosure burden and does so well: it states the return format (structured JSON rows), the shape of the data (dataType of post/comment/user/community), and the specific behavior of user-profile URLs (returns the user's posts and comments). It leaves rate limits, error handling, and auth needs undisclosed, which is the gap keeping it from a 5.

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?

Three sentences with no waste: the action is stated first, followed by concrete URL-style examples, and closes with the output data type. Every sentence earns its place and the examples are tightly packed.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description covers the essential decision points: acceptable URL patterns, per-URL behaviors, and the returned dataType field. Slight gaps are the includeNsfw semantics and quirks like search-result page parity with search_reddit, but the main calling scenarios are well covered.

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 only 40% schema description coverage, the description compensates meaningfully: it supplies exact URL format examples for the un-documented 'urls' parameter and clarifies behaviors around comments/threads. Parameters includeNsfw and maxCommentsPerPost none by description to un-documented; their purpose remains implied, but the core urls semantics are materially enriched.

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 opens with a specific verb-resource pairing ('Scrape specific Reddit URLs') and enumerates exactly four supported URL shapes: post permalinks, user profiles, subreddit listings, and search-result pages. This level of enumeration makes it easy to distinguish from siblings like search_reddit and scrape_subreddit without opening their schemas.

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 implicitly routes the agent: it states this tool is for specific Reddit URLs, implying that scrape_subreddit is the alternative for whole subreddits and search_reddit for queries. However, it never explicitly names the sibling tools or gives when/not-to-use exclusions, which stops it short of a 5.

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