reddit_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Search Reddit posts' and does not mention whether results include post content, metadata, or how results are paginated. It also does not disclose any side effects (though search is implicitly read-only) or authentication requirements. The description is too sparse to inform an agent of expected behavior beyond the obvious.

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, well-formed sentence with no extraneous words. It is front-loaded with the core purpose and immediately states the optional subreddit scoping. There is zero fluff, making it highly efficient.

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 search tool with five parameters, no output schema, and no annotations, the description is critically incomplete. It does not specify the return format (e.g., list of post IDs, full posts, metadata), how to control result count or ordering (sort, limit, time_filter), or any pagination behavior. An agent would need to infer these details from the schema alone, which is insufficient 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 only 40%, with only 'query' and 'subreddit' described in the schema. The description adds no explanation for 'sort', 'limit', or 'time_filter', which have enums and defaults but no textual descriptions. The description mentions 'across all communities or within a specified subreddit', which indirectly relates to query and subreddit, but does not compensate for the undocumented parameters. An agent would not know the meaning or usage of sort or time_filter from this description.

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 clearly states the tool searches Reddit posts, either globally or within a specified subreddit. This distinguishes it from siblings like reddit_browse_subreddit (which likely browses a subreddit's content) and reddit_read_thread (reading a specific thread). The verb 'search' and resource 'posts' are specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as reddit_browse_subreddit or reddit_read_thread. The description does not mention any exclusions, prerequisites, or context where this tool is preferred. It only states the capability without situating it among siblings.

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