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

Goes well beyond the readOnly/idempotent annotations by disclosing the ~1,000-item pagination ceiling, the per-comment credit cost model, the NSFW filtering side effect surfaced via meta.omittedNsfw, and the exact 404 semantics for missing vs suspended accounts. This is precisely the operational context annotations cannot carry.

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?

Front-loads the core action and return shape, then layers edge cases and cost/pagination notes in a compact block. Every sentence carries actionable information with no restatement of the name or title.

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 still names the key return fields (linkTitle, linkPermalink), the pagination cursor location, and the omission metadata, and covers error states. An agent has everything needed to call and interpret results correctly.

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 already 100%, so the baseline is 3, but the description adds real value on cursor: it explains that meta.nextCursor must be passed unchanged and is bound to the other parameters, and it clarifies that a short or empty page may be NSFW filtering rather than inactivity.

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 — listing an account's comments across every community, with the parent post fields named. It distinguishes itself implicitly from get_reddit_user_posts by resource type but never names any sibling to route against.

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?

Gives concrete operating conditions: empty page with karma means hidden activity, nonexistent account is 404, suspended is 404 with details.reason, and it tells the agent to call again with cursor when meta.nextCursor is set. It stops short of explicitly saying when to prefer this over get_reddit_user_posts or get_reddit_comments.

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