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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the sentence "Read-only: returns public data and changes nothing" largely restates them. The genuinely additive piece is "Costs 1 credit per request," which is real behavioral context not captured anywhere in structured fields; nothing is said about rate limits, auth, or pagination behavior.

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 very short sentences are front-loaded and waste little, but the title is repeated verbatim as the first sentence and the read-only line duplicates annotation data, so roughly two of the three sentences add little that structured fields don't already convey.

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 no output schema, the description should hint at what comes back (post objects plus a nextCursor for paging) since the cursor parameter only makes sense in that context. Annotations cover the safety profile and the schema covers inputs, so the tool is usable, but the return-side and cost-per-page implications are left unstated.

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 sort, time, count, cursor and subreddit are all documented with enums, defaults and bounds in the schema itself. The description adds no meaning beyond that, making the baseline 3 correct.

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?

"List posts in a subreddit feed" gives a specific verb and resource, and the subreddit-scoped nature distinguishes it in practice from reddit_search_posts and reddit_list_user_posts. It never names those siblings, though, so the differentiation must be inferred from the tool name rather than stated.

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 scope implies when to reach for this tool (enumerating a community's feed rather than searching or fetching a single post), but there is no explicit when-to-use, when-not-to-use, or pointer to reddit_search_posts / reddit_get_subreddit. The credit-cost note gives a budgeting cue but not behavioral routing guidance.

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