Subreddit Search

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

With readOnlyHint=false, an agent could wrongly assume a mutating/side-effecting call; the description resolves this by explaining that read-like POST requests do not publish to social platforms. It also discloses credit consumption and the confirm=true gate, which annotations do not cover.

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?

Front-loaded with the core action, then return shape, then the credit/confirm caveat. The return-field enumeration is somewhat long but earns its place because there is no output schema. No filler sentences.

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, describing the returned post/comment/media fields is necessary and done well, and pagination via cursor plus the credit/confirm gate are covered. Auth/account credential behavior is left entirely to the schema description, which is the only material gap.

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 every parameter (including the enum constraints on sort and timeframe) is already documented in the schema. The description adds sort/timeframe/pagination support at a high level but no syntax or semantics beyond the schema; baseline 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 ('searches') plus resource and scope ('within a specific subreddit') and enumerates the three content types returned (posts, comments, media). This distinguishes it from the broader reddit_search and from the listing-style reddit_subreddit_posts, though no sibling is named explicitly.

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 establishes the operational precondition that the call 'requires confirm=true' and may consume paid credits, which is genuine usage guidance. However, it never says when to choose this over reddit_search or reddit_subreddit_posts, so selection guidance among near-identical siblings is only implied.

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