get_subreddit_feed

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

The annotations already declare readOnlyHint=true, so the safe-read behavior is covered. The description adds the 'current posts' scope and sort options, which aligns with the schema enum, but it does not discuss pagination, limit behavior, account handling, or return characteristics. This is adequate given the read-only annotation.

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 efficient sentence with no filler, and the sort options are packed into a clear parenthetical. Every word contributes to the meaning.

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 simple read-only feed with an output schema and readOnlyHint, the core invocation is inferable. However, the minimal text leaves gaps around account/limit semantics and how this tool differs from search_subreddit or get_subreddit_sidebar, so completeness is average.

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 should compensate, but it only repeats the sort enum ('hot, new, rising') without explaining the required 'subreddit' format, the meaning of 'limit,' or the optional 'account' parameter. The added semantic value over the schema is minimal.

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 states the resource (subreddit) and scope (current posts) along with the sort modes, which makes the tool's purpose clear and distinguishes it from sidebar or post-detail siblings. It lacks an explicit verb like 'retrieve' or 'list,' but the intent is unambiguous.

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 guidance is provided about when to use this tool instead of siblings such as get_subreddit_sidebar or search_subreddit, nor are any conditions or exclusions given. The usage context must be inferred entirely from the name and the phrase 'current posts.'

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