List Subreddit Posts

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

With no annotations provided, the description must carry full behavioral disclosure. It does reveal the return format (JSON with posts and meta) and pagination fields (limit, has_more, next_cursor), which is helpful. However, it does not mention error handling (e.g., invalid subreddit), rate limits, or authentication requirements. This is adequate but not rich enough for a higher score.

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 two sentences long, front-loaded with the core purpose, and every clause adds value. It lists the supported listing types and the return structure without any fluff. This is an exemplary concise structure.

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 moderate complexity (5 params, no output schema, no annotations), the description covers the essential behavior: what it lists, the return format, and pagination. It could be more complete with usage guidance or error behavior, but the combination of the description and thorough schema makes it sufficiently complete for an agent to use correctly.

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%, so the description does not need to add much parameter detail. It does mention listing types and pagination cursor, which slightly enriches the schema. However, most parameter semantics are already fully described in the schema, so the description adds marginal value. Baseline 3 is appropriate.

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 lists posts from a subreddit and enumerates the supported listing types (hot/new/top/rising/controversial). This distinguishes it from sibling tools like reddit_get_post (single post) and reddit_search (search across subreddits). The verb 'List' and resource 'posts from a subreddit' make the purpose 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 gives clear context about what the tool does (list posts from a subreddit) but does not explicitly mention when to prefer this over alternatives or any exclusions. It implies usage for browsing a subreddit's posts but lacks guidance on when not to use it, such as searching for specific posts or retrieving a single post.

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