reddit_post_comments_listList comments on a Reddit post by URL. Returns a list (use cursor when paginated).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Link to the Reddit post. | |
| trim | No | When true, requests a lighter response shape when available. | |
| cursor | No | Opaque cursor from a previous response to fetch another page of comments or replies. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, establishing safety and dynamic nature. The description adds behavioral detail by stating it 'Returns a list (use cursor when paginated)', which discloses the return type and pagination mechanism. This goes beyond annotations and helps the agent understand output handling, though it doesn't cover rate limits or auth.
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 two crisp sentences with zero filler. The primary purpose is front-loaded, and the behavioral note on pagination is appended succinctly. Every word adds value, making it highly efficient for agent parsing.
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?
The tool is simple with 3 parameters and no output schema. The description covers the core action and pagination behavior. While it doesn't describe the comment object shape, the absence of an output schema makes that optional. The schema handles parameter details, so the description is adequately complete for an agent to call the tool 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 100%, with clear descriptions for all three parameters (url, trim, cursor). The description adds nothing substantially new about parameters beyond reinforcing that cursor is for pagination, which the schema already states ('fetch another page'). Baseline 3 applies because the schema fully documents parameters.
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 states exactly what the tool does: 'List comments on a Reddit post by URL.' It identifies the resource (Reddit post), the operation (list comments), and the input method (URL). This clearly differentiates it from sibling comment-list tools on other platforms like facebook_post_comments_list or youtube_video_comments_list.
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 does not explicitly mention when to use this tool versus alternatives or exclude any usage. It implies usage for Reddit post comments, but does not name related tools (e.g., reddit_post_get for post details) or state conditions when not to use it. The clear purpose partially compensates, but explicit guidance is absent.
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 clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.
All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).
The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.
The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.