browse_subreddit

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

No annotations are provided, so the description carries the burden of behavior disclosure. It is upfront that scores, upvote ratios, and comment counts are unavailable, and it explains the 'new' sort behavior. It could go further by stating read-only/no-auth expectations or rate limits, but this is still useful behavioral context.

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?

Everything in the description earns its place: purpose, usage guidance, limitations, then parameter details. The most decision-relevant content is front-loaded, and the parameter documentation is compact without being padded by schema repetition.

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 input parameters are thoroughly covered and the description calls out key data limitations, which is especially important since there is no output schema. It stops slightly short of describing the exact shape of the returned posts, but it is complete enough for an agent to select and invoke 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?

The schema provides only type/default values with 0% description coverage, but the Args section fully compensates. It documents subreddit prefix handling, allowed sort values, when time_filter applies, and the limit range 1-100, adding real meaning beyond the 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?

Opens with 'Read what a subreddit is posting right now', giving a specific verb, a concrete resource (a subreddit), and the scope of live community activity. It also distinguishes itself from the sibling search tool by calling out posts too recent for the search index and clarifying that the 'new' sort does not lag.

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?

Explicitly says 'Use this when...' and supplies concrete scenarios: questions about what a community is currently saying, or posts too recent for search indexing. It contrasts with search behavior, but it does not explicitly state when to prefer get_post over this tool.

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