Browse Subreddit

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

Annotations already declare readOnlyHint and openWorldHint, and the description usefully adds the return envelope and, critically, the RSS fallback degradation (max ~25 posts, no score/comment counts, no pagination) — non-obvious behavior an agent would otherwise miss. It omits auth/rate-limit details, keeping it below a 5.

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 tightly-packed sentences, front-loaded with the core action then the safety profile and return shape, then the fallback caveat. Every clause carries information the agent needs.

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 correctly supplies the return shape and pagination cursor semantics, and covers the degraded fallback path. It could say more about pagination termination or empty results, but it is sufficient to call the tool correctly.

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, after, limit, subreddit and time_filter are all already documented in the schema. The description repeats the sort enum without adding syntax, defaults, or interaction detail beyond what structured fields provide, so 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 (browse) and resource (subreddit feed) with the supported sort modes enumerated, so an agent immediately knows the scope. It stops short of naming which sibling to prefer (search_reddit, get_top_posts, get_trending_subreddits), so differentiation is left to inference.

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?

Usage is implied by 'Read-only, anonymous' and the option set, but there is no explicit when-to-use-vs-alternative guidance against the many sibling subreddit/post tools. An agent can guess it is the general feed reader, but nothing states when to reach for search_reddit or get_top_posts instead.

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