Get Post

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

With no annotations, the description carries the full burden. It discloses that the tool returns JSON with post and comments, and clarifies nesting behavior ('top-level comments include one nested level of replies'). This adds useful behavioral context beyond a simple 'fetch post' statement.

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?

Two sentences, front-loaded with the verb 'Fetch', no filler. The key detail about comment nesting is included efficiently.

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?

No output schema exists, but the description provides a high-level return format ('Returns JSON with post and comments') and comment nesting detail. For a 3-parameter read tool with 100% schema coverage, this is adequate. It doesn't mention error cases or pagination, but those are less critical for a simple fetch.

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% (all three parameters have descriptions). The description adds minor context by clarifying 'by id' and that comments are included, but the schema already documents post_id, comment_sort, and comment_limit fully. Baseline 3 is appropriate.

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 'Fetch a Reddit post (submission) by id along with its comments', which is a specific verb+resource+scope. It distinguishes from sibling tools like reddit_get_comment (which fetches a comment) and reddit_list_posts (which lists posts).

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 implies when to use: when you need a post by ID with its comments. However, it doesn't explicitly contrast with sibling tools like reddit_get_comment or mention alternatives, so it's clear context but lacks explicit exclusions.

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