reddit_trends

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

With no annotations, the description carries the full behavioral burden. It adds valuable context by stating the output is 'normalized public posts' and discloses the 503/Retry-After rate-limiting behavior. While it doesn't detail the return structure or pagination defaults, it goes beyond the raw schema and gives the agent useful expectations.

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 three concise sentences. The first states the core purpose, the second provides a clear alternative, and the third gives practical error-handling advice. Every sentence earns its place with no fluff or 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?

For a simple list tool with no required parameters and no output schema, the description is quite complete. It covers purpose, scope, alternatives, and rate-limiting behavior. It doesn't detail the exact return object, but 'normalized public posts' gives a reasonable expectation. This is a solid, well-rounded description.

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 input schema already provides 100% coverage for all parameters (sort, time, after, limit), so the baseline is 3. The description doesn't add additional parameter-level meaning beyond what the schema already explains, so no extra credit is warranted.

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 opens with a specific verb+resource: 'List Reddit trends.' It further clarifies scope as 'broad Reddit hot, new, rising, or top feeds' and explicitly distinguishes itself from subreddit-specific tools by pointing to an alternative endpoint. This makes the purpose unmistakable and differentiates it from sibling Reddit tools.

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 explicitly states when to use this tool (for broad Reddit trends) and gives a clear alternative: 'For subreddit-specific trends, use `/reddit/subreddit/{subreddit}/posts` with sort=hot, sort=new, sort=rising, or sort=top.' It also provides actionable guidance for handling 503 throttling responses, which helps the agent decide when retrying is appropriate.

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