get_post

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

With no annotations, the description carries the burden and does real work: it discloses output shaping (nested replies preserved, false flags and empty replies omitted), the more_id/comment_id expansion loop, and an untrusted-content/prompt-injection warning. It omits read-only status, rate limits, and failure behavior (e.g., nonexistent post).

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-loaded with the core action, then parameter routing, the expansion workflow, and the safety note. Dense but every clause carries information; the boolean-flag parenthetical is the only mildly incidental detail.

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 six params, no output schema, and no annotations, the description covers enough: what is returned, how comments nest, how to expand collapsed subtrees, and how to address the post. Return-value details beyond shape (pagination, limits) remain unstated.

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%, so the baseline is 3. The description adds value by framing url versus subreddit+postId as mutually exclusive alternatives and by connecting comment_id to the more_id value surfaced in output, a link the schema alone does not make.

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: fetching a single Reddit post plus its threaded comments. The scope (one post + comment tree) implicitly separates it from get_subreddit_posts and search_reddit, but no sibling is named explicitly, so it stops short of a 5.

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 clear invocation context: 'Pass subreddit+postId, OR a full reddit url', and explains the follow-up pattern for collapsed subtrees. It does not say when to prefer this over search_reddit or get_subreddit_posts, so there are no exclusions or alternative routing.

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