get_subreddit_posts

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

With no annotations, the description carries the full disclosure burden and does well: it names the return fields (id, subreddit, next_after) and adds a genuine safety trait — that returned titles/bodies/comments are untrusted user content to be treated as data. Missing only auth/rate-limit context.

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 dense sentences with no filler; return shape and pagination come before the safety note, and every clause earns its place.

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?

No output schema exists, so the description correctly fills that gap by describing the returned fields and the pagination cursor, and it flags the untrusted-content risk. Nothing essential for calling the tool correctly is missing.

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 sort, time, after, limit, and subreddit are already documented. The description restates the sort enum and reinforces the pagination cursor flow but adds no format or constraint detail beyond the schema. Baseline 3 applies.

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?

States a specific verb (Get) and resource (posts from a subreddit), enumerates the sort modes, and distinguishes itself from get_post by naming it as the follow-up tool. An agent can tell it apart from siblings like search_reddit without opening any schema.

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?

Gives clear context: browse a subreddit's listing, then follow up with get_post using returned id+subreddit, and paginate with next_after. It stops short of an explicit when-not or a direct contrast with search_reddit, which is the closest alternative.

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