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

Annotations already declare openWorldHint=true and destructiveHint=false, so the description's bar is lower, but it adds nothing beyond them: no mention that results are paginated via the after cursor, no rate-limit or auth context. Notably readOnlyHint=false on a search tool is unexpected, and the description neither confirms nor explains any side effect.

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?

A single front-loaded sentence with zero waste. It is under-specified rather than bloated, so the terseness is a clarity problem, not a conciseness one.

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?

An output schema exists, so return values need no explanation, and the schema covers all parameters. What is missing is the operational framing: what corpus is searched, that results are paged, and how this relates to the generic api_request sibling.

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 query, limit, and after are fully documented in the schema itself. The description adds no meaning beyond that, which is acceptable at this coverage level but earns no credit.

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 names a specific verb and resource ("Search Reddit posts"), so the basic operation is clear. However, it does nothing to separate this tool from siblings like api_request or the other platform-specific tools (x_tweets, instagram_media), and it never states what scope of Reddit is searched (subreddit, user, all of Reddit).

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?

There is no guidance on when to use this versus api_request or list_endpoints, and no exclusions. An agent must infer that this is the Reddit-specific path for post search purely from the name.

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