browse_subreddit

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

Beyond the readOnlyHint annotation, the description discloses the data_source field behavior, null fields when using RSS, and warns not to infer popularity from RSS data. This gives full transparency on credential-dependent output differences.

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 efficiently cover purpose and credential behavior. Every sentence adds value; no redundant or vague wording.

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?

The description explains the return structure, credential dependency, and field differences. It lacks details on pagination (e.g., how to get more than limit results) but given no output schema and basic read operation, this is acceptable.

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?

The description adds minimal extra meaning beyond the schema: it mentions sort choices in text, but does not elaborate on 'time', 'include_nsfw', or 'include_subreddit_info'. With 50% schema description coverage, the description does not fully compensate, though it provides context on credential effects.

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 clearly states the tool fetches posts from a subreddit with sorting options, and the return includes a data_source field. This distinguishes it from sibling tools like search_reddit (searching across Reddit) and get_post_details (single post).

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 explains how results differ based on Reddit credentials, guiding when each behavior applies. It does not explicitly state when not to use this tool versus alternatives, but the context from sibling names and the description itself implies browsing vs searching.

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