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

Beyond the read-only and open-world annotations, it discloses the public-data scope, the absence of comment fetching, credit charges, variable pricing, and the possibility that repeated requests purchase data again. The pricing information is valuable but confusing because the 10-credit minimum and later 1-credit figure are not cleanly reconciled, and the mention of requested options does not match the single-parameter schema.

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 purpose, output fields, and supported inputs are front-loaded and efficiently presented. The trailing pricing block is repetitive and contains copy-paste artifacts such as 'Reddit Post API View Pricing' and 'Get information from a Reddit post without comments,' making the definition longer and less polished than necessary.

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 simple one-parameter lookup with no output schema, the description covers the essential inputs, returned fields, comment exclusion, and cost/retry behavior needed to invoke it appropriately. Explicit sibling alternatives and clearer, consistent pricing would make it fully dependable.

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?

Although the schema provides no description for url, the description explains that it must identify a public Reddit post and names two accepted URL forms: canonical post URLs and Reddit mobile share URLs. This substantially compensates for the missing schema documentation, though concrete examples or unsupported URL forms would make it more precise.

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 opening sentence gives a specific verb, resource, input, and scope: retrieving public Reddit post details by URL without comments. The enumerated return fields and explicit comment exclusion also distinguish it from Reddit comment and transcript siblings.

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 clearly establishes that this is for post-level details from canonical or mobile share URLs, and not for fetching comments. It does not explicitly route agents needing comments, transcripts, or post discovery to social_reddit_post_comments, social_reddit_post_transcript, or social_reddit_search.

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