reddit_post

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the basic retrieval action and restates parameter defaults already present in the schema. It does not mention how comments are structured, whether limits are total or per-thread, pagination, authentication, or error behavior.

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 and front-loaded with the main action. The Args block is somewhat redundant with the schema but adds useful semantic hints, so it earns its place. There is no filler or excessive 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?

An output schema exists, so return structure is handled elsewhere. The description gives enough information to make a basic call with all parameters, but it lacks usage context, behavioral caveats, and clarity on parameter semantics. It is adequate for simple invocation but incomplete for nuanced decisions such as sibling selection or understanding thread traversal behavior.

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 description coverage is 0%, so the description must compensate. The Args section adds one-line meanings for all three parameters, which is helpful: post_id is the Reddit post ID, comment_limit is comments to fetch, comment_depth is thread depth. However, these descriptions are shallow and ambiguous, leaving questions about post_id format and how depth/limit are counted.

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 begins with a clear verb and resource: 'Get post content and comments.' This unmistakably indicates fetching a specific post and its comments, which is distinct from sibling tools that focus on listings or topic feeds. The name reddit_post reinforces this single-post scope.

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?

Usage can be inferred: the tool is for retrieving a Reddit post and its comments. However, there is no explicit guidance about when to prefer this over siblings such as reddit_info, reddit_hot, or reddit_new, and no mention of when not to use it. The context is implicit rather than stated.

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