search_subreddit

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

With readOnlyHint=true already present, the description does not need to disclose read-only behavior. However, it adds no extra behavioral context such as rate limits, auth requirements, or edge cases (e.g., empty results). It only restates the core purpose without going beyond the annotation.

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?

The description is a single, front-loaded sentence with no redundant words. It efficiently communicates the tool's core function, earning its place without any fluff.

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?

Despite the output schema and annotations providing some structure, the description is too sparse for a 5-parameter tool with 0% schema coverage. The purpose of the 'account' parameter and any usage constraints are unclear, making the overall package incomplete for confident 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 description coverage is 0%, and the description only implicitly maps 'subreddit' and 'keywords' to the subreddit and query parameters. The sort, limit, and account parameters are left unexplained, so the description fails to compensate for the absent schema-level descriptions.

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 states a specific verb ('Search'), a resource ('within one subreddit'), and scope ('for keywords'). This clearly distinguishes it from broad Reddit search or feed retrieval tools, though it does not explicitly name any sibling 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?

The description provides no guidance on when to use this tool versus alternatives like search_mentions or get_subreddit_feed. There are no explicit exclusions, prerequisites, or conditional usage hints, leaving the agent to infer applicability from the name and snippet alone.

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