Reddit posts

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

With no annotations, the description carries the full burden. It discloses the output fields (title, body, upvotes, awards, subreddit), giving the agent a reasonable expectation of the return payload. However, it does not describe error behavior, rate limits, authentication needs, or any side effects, leaving gaps in transparency.

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 sentence that quickly communicates the tool's core output. It is front-loaded and free of fluff, earning a good conciseness score. However, it could include a bit more context without becoming verbose.

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?

For a tool with only one parameter and no output schema, the description is minimally adequate. It states the purpose and basic output fields, but lacks usage context, alternatives, or constraints. The overall simplicity of the tool makes this acceptable, though not exemplary.

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 100% of parameters (one 'url' field described as 'Reddit post URL'). The description does not add any additional meaning beyond the schema, so the baseline of 3 applies.

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 identifies the resource (Reddit posts) and the data type returned (structured post data with specific fields). It distinguishes from sibling tools like web_data_reddit_comments by focusing on posts rather than comments. Lacks an explicit action verb, but the intent is unambiguous.

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 guidance is provided about when to use this tool versus alternatives. The description does not mention that web_data_reddit_comments exists for comment data, nor any exclusions or prerequisites. Usage is implied only by the tool name and resource type.

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