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

Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add operation-specific behavior, which it does: absent ids return 404, and the id is a composite of subreddit, snapshot date, and rank. It stops short of saying whether the returned snapshot is immutable/point-in-time or how large the payload is, so it is strong but not exhaustive.

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 short sentences, front-loaded with the action and scope, then the id contract, then the routing pointer. No filler or redundant restatement of the tool name.

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 single-parameter lookup with an output schema defined and readOnly annotations, the description covers what it does, where the id comes from, and the failure mode. Missing only lower-value details such as what a "snapshot" contains or whether stale/expired snapshots behave like absent ids.

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% and the single parameter's schema already states "exact subreddit:date:rank post_uid returned by datasets_reddit_trending_search." The description restates the same composition detail, adding only the exactness requirement and the 404 consequence, so the baseline 3 is appropriate.

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 and resource ("Fetch one stored trending-post snapshot") and scopes it to a single post_uid, which cleanly separates it from the multi-result sibling datasets_reddit_trending_search and datasets_reddit_trending_facets. An agent can tell what this returns without opening the 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 explicitly states where the required id comes from ("from datasets_reddit_trending_search") and repeats the routing instruction in the closing sentence ("Use datasets_reddit_trending_search to find post ids"). It also conveys that the call only works with an exact known id, which implicitly rules out using this tool for discovery.

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