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

Annotations declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is already covered. The description goes well beyond that with a cost model ($0.003 per page), pagination limits (25 per page, up to ~500), the full return-field list, and the cross-parameter rejection rule for posted_ago.

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?

A single dense paragraph front-loads the core action and scope, then layers options, return shape and pricing. Every clause carries information; nothing is repeated or padded.

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 read-only, no-output-schema tool the description covers what an agent needs: what it fetches, the feeds and sorts available, the returned fields, the pagination ceiling, and the billing rate. Nothing material is missing.

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 every parameter, including the 'Rejected with any other sort_by' constraint. The description restates the same enum options (feed, sort_by, posted_ago) without adding syntax or format detail beyond the schema, 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?

States a specific verb (Get) and resource (posts trending across Reddit), then names the exact scope: r/popular (feed=popular) or r/all (feed=all). This clearly separates it from subreddit-scoped siblings like reddit_subreddit_posts and query-based search_reddit without needing their schemas.

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 explains parameter-validity rules (country only with feed=popular; posted_ago only with top/controversial), which is useful usage context. However, it never states when to choose this tool over alternatives such as reddit_subreddit_posts or search_reddit, so tool-selection guidance is only implied by scope.

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