reddit_subreddit_posts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral detail about output fields and pagination ('plus an `after` cursor for paging'), which is beyond what annotations provide. No contradictions.

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?

Four sentences, front-loaded with the primary purpose, no redundant words. Every sentence adds value: purpose, usage, return values, and an example. Highly concise.

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?

For a 5-parameter read-only list tool with no output schema, the description covers purpose, usage, return fields, pagination cursor, and provides an example. The annotations cover safety. This is fully sufficient for an agent to select and invoke the 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?

Input schema has 100% description coverage for all 5 parameters, so the baseline is 3. The description adds an example ('subreddit=programming sort=top t=week') that clarifies how the parameters combine, and clarifies the `t` parameter's role (only for 'top'/'controversial') is already in schema, but the example adds value. Thus a 4 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 uses a specific verb phrase 'List posts from a subreddit by sort order' and clearly identifies the resource and action. It distinguishes from sibling search/comment tools by framing this as reading a community's feed. The mention of return fields (title, author, score) adds further specificity.

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 explicitly states 'Use this to read a community's feed' with sort options (newest, hot/trending, top-of-week, rising), providing clear context for when to invoke. It does not name alternative tools or exclusions, so it stops short of a full 5, but the usage context is unambiguous.

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