reddit_search

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

Annotations already mark the tool as read-only, so the description doesn't need to cover safety. It adds useful behavioral context beyond the annotation by explaining that Reddit's search index is weaker than web search engines and that relevance/time=all typically outperforms `new` for canonical threads. It doesn't discuss return format, but that's a minor gap for a read-only search tool.

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 concise sentences with no filler: the action and scope are first, followed by two high-value search-strategy tips. Every sentence earns its place.

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 read-only search tool with six well-documented params, the description covers the essential decisions: scope, query style, and sort/time strategy. There is no output schema, so return-format details are not explicit, but the sibling tools and the parameter descriptions provide enough surrounding context for correct invocation.

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 baseline is 3. The description adds value beyond the schema by advising query formulation ('a few distinctive words over a natural-language question') and by clarifying the interaction of `sort` and `time` for the canonical-thread use case. This goes beyond the raw parameter definitions.

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 opens with the specific action and resource, 'Search Reddit,' and immediately clarifies the scope behavior: subreddit-specific when `subreddit` is provided, site-wide otherwise. This also distinguishes it from sibling listing/getting tools, which are about browsing or retrieving posts rather than searching.

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?

The description gives clear invocation guidance: provide `subreddit` for scoped search and use distinctive keywords rather than natural-language queries. It also advises on `sort` and `time` settings for finding the canonical thread, but it does not explicitly name alternative sibling tools or state when not to use this tool.

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