reddit_user_posts

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context: output is 'normalized,' only public posts are returned, and a 503 with Retry-After indicates throttling with a specific retry guidance. However, it does not mention auth expectations, pagination response shape, or other error modes.

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 with no filler. The first sentence states the core purpose, and the second adds a valuable operational note about throttling. It is well-structured and front-loaded.

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 simple list tool with three parameters, all schema-documented. The description covers purpose, output normalization, public-only scope, and an important throttling behavior. With no output schema, return details are somewhat vague, but for a straightforward feed-listing tool this is reasonably complete.

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?

All three parameters (username, limit, after) are already described in the input schema, with limit's default and clamp behavior explicitly documented. The description adds little beyond the phrase 'submitted feed,' which is a minor clarification rather than significant new parameter semantics.

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 starts with a specific verb and resource: 'List Reddit user posts.' It further clarifies scope by noting it returns 'normalized public posts from a public Reddit user's submitted feed,' which clearly distinguishes it from sibling tools like reddit_user_comments or reddit_search.

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 usage context by emphasizing 'public Reddit user's submitted feed,' but it does not explicitly state when to choose this over alternatives such as reddit_user_comments, reddit_subreddit_posts, or reddit_search. No exclusions or alternative-tool guidance are provided.

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