browse_subreddit

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

With no annotations provided, the description carries full burden. It discloses the tool's behavior (fetching posts, sorting options, return content) but doesn't mention important behavioral traits like rate limits, authentication requirements, pagination behavior, error conditions, or whether this is a read-only operation. The description is adequate but lacks depth for a tool with 6 parameters.

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 that efficiently convey the core functionality and return value. Every word earns its place with zero waste - first sentence covers action, resource, and key parameter (sort), second sentence describes return content. Well front-loaded with essential information.

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?

For a tool with 6 parameters, no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and return format but lacks important context about behavioral constraints, error handling, and detailed usage scenarios. The 100% schema coverage helps, but the description itself doesn't provide complete guidance for optimal tool invocation.

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 the schema already documents all 6 parameters thoroughly. The description adds minimal value beyond what's in the schema - it mentions sorting choices and return content, but doesn't provide additional semantic context about parameter interactions or usage patterns. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('fetch posts'), resource ('from a subreddit'), and scope ('sorted by your choice'). It distinguishes from siblings by focusing on bulk post retrieval rather than individual post details (get_post_details), search (search_reddit), user analysis (user_analysis), or explanations (reddit_explain).

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 implies usage for retrieving sorted post lists from subreddits, but doesn't explicitly state when to use this versus alternatives like search_reddit for keyword-based queries or get_post_details for individual posts. It provides context about sorting options but lacks explicit guidance on tool selection.

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