browse_subreddit

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

Adds value beyond readOnlyHint=true annotation by clarifying it 'works anonymously', explaining time_filter only applies to top/controversial, describing return shape, and noting the after cursor. Strong context beyond annotations.

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 sentences, information-dense, purpose front-loaded, every clause earns its place. Covers tool purpose, behavioral notes, return shape, and alternatives without redundancy.

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?

Given 5 optional params (0 required), full schema descriptions, and rich annotations, the description covers all essential context: default behavior, pagination, auth model, and edge cases. Nothing material is missing.

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 100% with good per-param descriptions, earning a baseline 3. Description adds cross-parameter semantics (omit subreddit → home feed, time_filter interaction with sort) and describes pagination behavior not in schema.

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?

Uses a specific verb (browse) plus resource (subreddit or home feed) with concrete sort orders. Explicitly differentiates from siblings by naming get_top_posts and search_reddit as alternatives with different purposes.

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?

States when to use this tool ('by sort order', 'by feed order') and explicitly directs to get_top_posts as a shortcut and search_reddit for keyword-based lookup. Clear when/alternatives guidance.

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