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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context beyond that: the Atom-feed fallback when the JSON surface is blocked, the default newest-first ordering, and the 1-credit cost. Pagination and rate-limit behavior are not covered, but the added fallback and cost details are meaningful.

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?

Three short sentences, front-loaded with the core purpose and scope, then useful behavioral notes. There is no filler and each sentence contributes.

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 six-parameter, read-only list tool with no output schema, the description covers purpose, default ordering, fallback behavior, and cost. However, it leaves parameter semantics (sort variants, timeframe, cache_max_age) and return/pagination structure largely unexplained.

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 coverage is 67%, with sort and cache_max_age lacking descriptions. The description's 'newest first by default' merely restates the schema default for sort and does not explain hot/top sorting, timeframe behavior, or cache_max_age. It does not compensate for the remaining schema gaps.

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 states a specific verb and resource: it returns posts submitted by a Reddit account, with default ordering. It is clear enough to distinguish from reddit_user (profile) and reddit_post (single post), though it does not explicitly name those 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?

There is no explicit guidance on when to use this tool versus reddit_search, reddit_user, or reddit_subreddit. The phrase 'newest first by default' hints at chronological listing, but no alternatives or exclusions are stated.

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