browse_subreddit

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

The description discloses key behaviors: uses RSS (no API key), returns specific fields, max 25 results, no scores/comment trees. This is transparent given no annotations exist. Could mention potential rate limits or error handling, but sufficient for simple use.

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 concise (4 sentences), front-loaded with the main purpose, then output details, limitation, and a tip. Every sentence adds value 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 no output schema and 4 parameters, the description covers purpose, output fields, limitation, and provides a usage tip. It lacks error handling or rate limit info, but is complete enough for a simple RSS-based tool.

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 75% (3/4 params documented). The description adds context beyond schema: no API key, RSS, returned fields, max results, limitation, and the 'all'/'popular' hint. This enhances understanding of parameters like subreddit and limit.

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 via RSS, lists the returned fields, and mentions the limitation of no scores/comment trees. It distinguishes from siblings by specifying it's for browsing subreddits and that 'all' or 'popular' can be used for cross-Reddit feeds.

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 provides clear context on when to use the tool (fetching posts via RSS, no API key) and gives a tip for cross-Reddit feeds. However, it does not explicitly state when not to use it or offer alternatives like search_reddit.

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