Get Reddit Post

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the bar is lower, yet the description adds value: it clarifies the call needs no authentication ('anonymous') and discloses that body text is 'truncated if very long' — a real behavioral trait not present in the schema or annotations. It does not discuss error behavior for missing/deleted posts.

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?

Two sentences, zero waste. The identity of the tool and its returned fields come first, and the disambiguation pointer is placed last where it belongs.

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?

With no output schema, the description compensates by enumerating the returned fields and flagging body truncation, so the agent knows what to expect. Parameter detail is fully carried by the schema. Nothing needed to invoke this read-only tool correctly is missing.

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%: both post_id (base36, fullname, or permalink) and the optional subreddit parameter are fully documented, including accepted prefixes. The description only reinforces 'by id' and adds nothing about parameter formats, 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?

States a specific verb and resource ('Fetch a single Reddit post by id') and enumerates the returned fields (title, author, subreddit, score, comment count, created time, permalink, link URL, body). It explicitly differentiates itself from get_post_comments, so an agent can pick it without opening either schema.

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?

It gives explicit routing guidance to a sibling: 'Use get_post_comments for the discussion.' That is a clear when-to-use-this-instead signal. It stops short of covering other plausible alternatives (search_reddit, get_top_posts) or exclusions such as multi-post retrieval, so it is not full 5-level guidance.

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