list_subreddit

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

With no annotations, the description must disclose behavioral traits. It only states 'public posts' implying read-only scope, but does not explain pagination, default sorting, rate limits, or the meaning of 'approved.' No output format or side effects are described, leaving significant ambiguity.

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 a single, focused sentence with no redundant words. It conveys the essential purpose immediately and does not bury key information.

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 has four parameters, no annotations, no output schema, and sibling tools, the description is too minimal. It fails to explain what the return value is, how parameters interact, or when to choose this over search_posts. The description alone is insufficient for correct tool invocation.

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 0%, so the description must compensate. It only mentions 'subreddit' indirectly and gives no insight into 'sort', 'limit', or 'time_filter' semantics. The schema itself is detailed, but the description adds no value to parameter understanding.

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 'List public posts from one approved subreddit' uses a specific verb (List) and resource (public posts) and clearly distinguishes this tool from siblings (search_posts, get_post, get_comments). It is concise and unambiguous about the tool's core function.

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?

No explicit usage guidance is provided. The description implies when to use it (to list posts from a subreddit) but does not mention alternatives or exclusions. Sibling tools like search_posts could be confused for this use case, yet there is no differentiation.

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