get_post_comments

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

Despite readOnlyHint and openWorldHint annotations, the description adds meaningful context: it is read-only (consistent) and 'works anonymously', and reveals that long threads are truncated with 'load more' stubs. This goes beyond annotations and desribes the tool's behavior clearly.

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 compact, front-loaded with the main purpose, and each sentence adds value: purpose, sort options, read-only, truncation behavior, and alternative tools. No redundant text.

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?

Although no output schema is provided, the description summarizes what is returned (post header, threaded comments with author badges, score, body, nesting depth, limit) and explains truncation behavior. This is sufficient for an agent to understand the tool's capabilities and expected output.

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 already covers all parameters with 100% coverage, so baseline is 3. The description adds extra value by clarifying that post_id can include a t3_ prefix, and that limit may still result in truncation due to threading. This goes above the schema's basic descriptions.

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 explicitly states 'Get the comment thread for a post (by post id + subreddit)' and enumerates sort options. It distinguishes from sibling get_reddit_post by noting that tool is for 'just the post body, not the thread', ensuring clear differentiation.

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?

Provides explicit guidance on when to use this tool (to fetch a comment thread) and when not (use get_reddit_post for post body). Also mentions get_more_comments for expanding truncated threads, giving a clear alternative path for further data.

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