reddit_get_comments

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

No annotations are provided, so the description carries full burden. It mentions old.reddit.com .json endpoints, which hints at unofficial API use, but it does not disclose read-only nature, rate limits, pagination behavior, or response format. The word 'Fetch' implies non-destructive, but this is not explicit.

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, front-loaded sentence with no unnecessary information. It efficiently conveys the core action and endpoint without filler or redundancy.

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?

An output schema is present, so return values are covered. The description is adequate for a simple read-only fetch with a well-documented schema, though it could benefit from explicit usage alternatives or behavioral context. Overall, it is complete enough for selection and invocation.

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 covers all 3 parameters with descriptions (shortcode, sort options, limit range), so schema coverage is 100%. The description adds no parameter-specific meaning beyond the phrase 'comment tree,' which indirectly relates to sort and limit. Baseline 3 applies because schema does the heavy lifting.

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 the tool fetches a post and its comment tree, using specific endpoints (old.reddit.com .json). The verb 'Fetch' plus the resource (post and comment tree) distinguishes it from siblings like reddit_get_posts and reddit_search.

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?

No explicit when-to-use guidance or alternatives are mentioned. The description implies it is for retrieving comments on a specific post, but it doesn't state when not to use it or reference sibling tools. The context is implied by the resource type.

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