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 by structured metadata. The description adds nothing further — no mention of pagination behavior, rate limits, private/suspended account handling, or what a response contains. Near-zero added value beyond the annotations.

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?

At four words it is short but under-specified rather than concise; it does not front-load any actionable information because there is none. Brevity here reflects missing content, not efficient editing.

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?

An output schema and annotations exist, so return values and safety need not be explained, but an agent still lacks any hint about when this tool is the right choice versus its Reddit siblings, or how the username/cursor interact. For a tool embedded in a large family of near-duplicate Reddit endpoints, the description is inadequate to disambiguate.

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 username, limit, and the 'after' pagination cursor are all documented in the schema itself (including the 1-100 range and cursor provenance). The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

"Reddit user posts" restates the tool name rather than stating a verb+resource with any specificity. It does imply fetching posts belonging to a user, which is marginally more than a pure tautology, but there is no verb (fetch/list/retrieve) and no differentiation from siblings like reddit_user_comments or reddit_subreddit_posts.

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, no exclusions, and no reference to the many siblings that overlap (reddit_user_comments, reddit_subreddit_posts, reddit_domain_posts, reddit_search). The agent is left to infer everything from the name alone.

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