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

The read-only/no-mutation claim merely restates readOnlyHint and destructiveHint=false, earning no credit. The genuinely new disclosure is "Costs 1 credit per request," which is real behavioral context absent from the annotations. Nothing is said about pagination limits or rate limiting beyond the per-request cost.

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 purpose, with no filler or hedging. The read-only sentence is largely redundant with the annotations, which is the only waste.

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 simple list tool with full schema coverage and complete annotations, the essentials are present, and the credit cost is a useful addition. However, with no output schema there is no statement of what post fields come back, and pagination behavior via cursor is left entirely to the schema.

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 every parameter (username formats, count bounds, sort/time enums, cursor) is already fully documented in the schema. The description adds no parameter meaning beyond that, which is the expected baseline of 3 when the schema carries the load.

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 and resource ("List a Reddit user's posts"), which is enough to separate it from reddit_list_user_comments and reddit_get_user by resource semantics. It does not explicitly name or contrast with any sibling, so it falls short of a 5.

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, when-not-to-use, or alternative routing is given. An agent must infer on its own whether to pick this versus reddit_list_user_overview, reddit_list_user_comments, or reddit_search_posts.

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