reddit-get-user-commentsGet comments submitted by a specific Reddit user.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort: hot, new, top, controversial | new |
| count | No | Number of results to return (default 10) | |
| username | Yes | Reddit username without u/ prefix | |
| time_filter | No | Time filter: hour, day, week, month, year, all | all |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond what annotations already declare (readOnly, idempotent, non-destructive). It simply restates the function without disclosing pagination, return format, or any potential edge cases.
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?
The description is a single, efficient sentence that gets straight to the point. No wasted words, well-structured for an AI agent to parse.
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 read-only tool with a well-documented schema and safety annotations, the description is minimally complete. It could mention sorting or count behavior, but the lack of an output schema and the simplicity of the operation make the one-liner sufficient.
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 covers all 4 parameters with descriptions, so the description does not need to add parameter semantics. It adds no extra detail, but the baseline of 3 applies due to high schema coverage.
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 clearly states the tool's action ('Get') and resource ('comments submitted by a specific Reddit user'), which distinguishes it from sibling tools like reddit-get-user-posts and reddit-get-post. It is specific and actionable.
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 guidance is provided on when to use this tool versus alternatives. It does not mention contexts or exclusions, leaving the agent to infer usage from the purpose statement alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is uniquely distinguished by platform prefix (reddit vs twitter) and specific action (get a post, get posts, search, etc.). No two tools have overlapping purposes, even within the same platform.
Tool names consistently use lowercase with underscores and a platform prefix, but the pattern is slightly mixed: Reddit tools use 'get' and 'search' as verbs, while Twitter tools include nouns like 'news', 'thread', and 'user-tweets' alongside verbs. Still, names are predictable and readable.
With 10 tools covering two major social platforms, the count is well-scoped. Each tool serves a distinct, meaningful purpose, and no tool feels redundant or unnecessary.
The tool set provides strong read coverage for both Reddit and Twitter, including search, post/thread retrieval, and user timelines. However, it lacks any write or interaction capabilities (e.g., posting, commenting, liking), which is a notable gap for a social media server and could limit agent workflows.