reddit-get-postGet detailed content of a specific Reddit post with comments.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | Reddit post ID | |
| subreddit | No | Subreddit name for faster lookup | |
| text_only | No | If true, return only id and title per post to save tokens. | |
| comment_limit | No | Number of comments to return (default 10) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds some context beyond the annotations by mentioning 'detailed content' and 'with comments', but it does not disclose behavioral traits such as response format, pagination, or the effect of parameters like text_only and comment_limit. The annotations already cover readOnly and destructive hints, so the description contributes modest extra context.
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 sentence of ten words, with no unnecessary repetition or padding. It is front-loaded and effectively communicates the core purpose in an extremely concise manner.
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?
Given the absence of an output schema, the description only vaguely mentions 'detailed content' without specifying the return structure or how comments are included. However, the full parameter schema and annotations cover the input and safety aspects, making the tool minimally adequate for an agent to invoke it, though expectations about output remain unclear.
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?
The input schema provides descriptions for all four parameters (post_id, subreddit, text_only, comment_limit), achieving 100% coverage. The description itself does not add meaning beyond what the schema already provides, so the baseline score of 3 applies.
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 that the tool retrieves a specific Reddit post and its comments, using a specific verb ('Get') and resource ('Reddit post'). It distinguishes itself from sibling tools like reddit-get-posts (plural) and reddit-search by emphasizing 'specific post' and 'comments', making its purpose unambiguous.
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 description provides no explicit guidance on when to use this tool versus alternatives. It does not mention when to prefer it over reddit-get-posts, reddit-search, or other siblings, nor does it state any prerequisites like having a post ID. Usage context is only implied by the word 'specific'.
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.