Browse a subreddit

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

Annotations only declare readOnlyHint and openWorldHint, so the description's disclosure that Reddit rate-limits RSS feeds hard, that calls are queued and spaced out, and that each call can take a minute or more is genuinely additive operational context. It stops short of describing failure/timeout behavior or pagination, keeping it out of the top band.

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?

Two sentences, zero filler, with the core listing behavior front-loaded and the latency warning immediately after. 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?

With no output schema, the description helpfully names the returned fields, and the rate-limit warning covers the main operational surprise. Minor gaps remain: no mention of how 'limit' interacts with rate limiting or what happens when a feed is unavailable.

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 coverage is 50%: subreddit format and the time/sort relationship are documented in the schema, while sort and limit carry only enums, defaults and bounds. The description restates the sort values but adds no new meaning for sort, time or limit, so it does not compensate for the undocumented half.

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 (list) plus resource (posts in a subreddit), enumerates the sort modes and the returned fields (title, URL, author, date, text). It is clearly distinguishable from get_thread and search_reddit in practice, but it never names those siblings to make the boundary explicit.

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?

There is no statement of when to use this versus get_thread or search_reddit, and no prerequisites or exclusions. The sort enumeration implies browsing modes, and 'call tools one at a time' is operational advice rather than tool-selection guidance.

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