reddit_trends

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

With no annotations provided, the description carries full burden. It states the tool 'returns normalized public posts' and implies read-only behavior via 'list'. It does not mention rate limits, authentication, or side effects, but the scope is clearly defined. A minor gap is the lack of explicit read-only confirmation, but the description is sufficient for safe usage.

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 two sentences, with the first sentence stating the purpose and the second providing an alternative. It is concise, front-loaded, and contains no filler. Every sentence earns its place.

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 the tool has 4 parameters, no output schema, and no annotations, the description provides adequate context for a simple list operation. It explains the tool's scope and offers an alternative. However, the return format ('normalized public posts') is vague, and no details about pagination (despite the 'after' parameter) are given. This leaves room for agent uncertainty.

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 baseline is 3. The description mentions sort values ('hot, new, rising, or top') which aligns with the schema but adds no new information beyond what the schema already provides. Parameters like 'after', 'limit', and 'time' are not elaborated in the description.

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's purpose: 'List Reddit trends. Returns normalized public posts from broad Reddit hot, new, rising, or top feeds.' The verb 'list' and resource 'Reddit trends' are specific, and it distinguishes itself from subreddit-specific trends by mentioning the alternative endpoint.

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 tells when to use this tool (for broad trends) and when not to: 'For subreddit-specific trends, use /reddit/subreddit/{subreddit}/posts...' It provides a clear alternative with corresponding sort values, offering excellent guidance.

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