reddit_list_posts

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

With no annotations, the description carries the full burden. It discloses pagination behavior ('Cursor-paginated') and the exact return shape, including the outputData schema. While it doesn't explicitly state there are no side effects, the term 'List' and the nature of the operation imply a read-only behavior. It adds meaningful context beyond the schema with the return format and flow position.

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 compact and efficient, with three sentences that cover purpose, pagination, return format, outputData contents, and flow context. Every sentence serves a distinct purpose with no redundant or ambiguous wording.

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?

Despite having no output schema, the description provides a comprehensive return structure including nested outputData fields. The flow context and pagination details make it complete for an agent to understand what the tool does and what to expect. There are no significant gaps for a list/pagination tool.

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 100%, so each parameter (limit, cursor, brandId) is already well-documented. The description adds a little value by explaining the cursor-pagination mechanism and the nextCursor link, which ties limit and cursor together. However, it doesn't provide additional semantics beyond the schema, so a baseline score of 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?

Clearly states the verb 'List' and the resource 'saved Reddit posts', and explicitly identifies them as outputs of reddit_rewrite. This distinguishes it from sibling tools like reddit_rewrite, reddit_suggest, and reddit_get_pool. The flow step naming also reinforces its specific role.

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 places the tool in a sequential flow: pool → suggest → rewrite → LIST_POSTS, which implies it is the final step to retrieve saved rewritten posts. It doesn't explicitly state when not to use it or name alternatives, but the flow context provides solid guidance for when this tool should be selected.

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