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

With no annotations, the description carries the full burden, and it discloses meaningful behavior: cost of 1 credit, no charge on empty results/failures, and the cache=true behavior with 24h hits and default fresh fetching. It does not mention rate limits or auth, but for a simple read tool the key behavioral traits are covered.

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?

Three tight sentences: first identifies the tool and its output, second states cost and failure policy, third explains the cache control. It is front-loaded with the most important information and contains no padding.

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 two-parameter tool with no output schema, the description is nearly complete: it lists the essential return fields, cost, failure policy, and caching. Missing explicit sibling routing is minor because the field list already clarifies scope. No output schema exists, but the described return fields give enough context for correct selection.

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 100%, so the baseline is 3. The description adds cache semantics ('Pass cache=true for a free 24h cache hit') but this largely restates the schema's cache field description. It adds no extra meaning for the required 'url' parameter.

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 states a specific verb ('Get'), a distinct resource ('a Reddit post'), and enumerates the exact fields returned (title, body, score, comments count, subreddit, author). This clearly separates it from siblings like reddit_post_comments and reddit_post_transcript.

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 it: whenever you need basic Reddit post metadata as JSON. But it never explicitly says 'use reddit_post_comments for the actual comments' or 'use reddit_post_transcript for a transcript', so guidance vs alternatives is only inferred from the sibling names and field list.

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