get_post

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

No annotations are supplied, so the description carries the full burden. It discloses the shape and depth of what is returned (full body, nested comment tree), which implies a read operation, but says nothing about authentication, rate limits, behavior on invalid or non-post URLs, or whether results are truncated by depth/limit.

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 tight sentences, with the capability statement front-loaded and the input-format note second. Nothing is wasted, though the URL example is largely redundant with the schema's format: uri plus description.

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?

There is no output schema, so the description must convey return values, and it does by naming body text, score, flair, and the nested comment tree. For a read-only fetch tool this is close to complete; only the depth/limit truncation behavior remains unstated.

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 coverage is 100%, so the schema already documents url, commentDepth, and commentLimit with defaults and bounds. The description only restates the URL format with an example and adds no meaning about how commentDepth and commentLimit interact or what truncation looks like, 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 uses a specific verb (Fetch) and resource (a full Reddit post) and enumerates what comes back: body text, score, flair, and the entire nested comment tree. That return-content detail clearly separates it from list-style siblings like get_community_posts or get_user_posts, though it never explicitly names an alternative.

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 is only implied: 'Use a direct Reddit post URL' states an input-format precondition, not a when-to-use rule. There is no guidance on when to prefer this over get_comment_permalink, resolve_url_type, or get_community_posts, and no when-not conditions.

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