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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no indication of pagination behavior (despite an 'after' cursor), result volume, or freshness. It contributes no 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?

The single four-word fragment is not concise so much as under-specified. There is no front-loaded verb or scope statement to anchor the agent.

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?

With an output schema present and annotations covering safety, the remaining burden is scope and usage, and the description supplies neither. For a tool whose 'broad trend' scope is ambiguous relative to many Reddit siblings, this leaves the agent guessing.

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 all four parameters (sort, time, after, limit) are already documented in the schema. The description adds no additional semantics, so the baseline 3 applies.

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 phrase 'Reddit broad trend posts' is a noun fragment that essentially restates the tool name 'reddit_trends'; there is no verb describing the operation (list? fetch? rank?). It hints at a 'broad' trend scope but does not distinguish this tool from reddit_search, reddit_subreddit_posts, or reddit_popular-style siblings.

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?

No when-to-use guidance is provided at all. Nothing tells the agent when to prefer this over reddit_search, reddit_subreddit_posts, or reddit_domain_posts, nor whether a subreddit or query is needed.

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