search_reddit

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 mentions the output format (formatted results with specific fields) and implies read-only behavior through 'search', but lacks details on rate limits, authentication needs, or pagination. It adds some context but is incomplete for a 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?

The description is well-structured with emoji icons and bullet points, making it easy to scan. It is front-loaded with the core purpose, followed by required/optional parameters, examples, and output details—all in a compact format with no wasted 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?

Given no annotations and no output schema, the description provides basic purpose, parameters, and output format, but lacks deeper behavioral context (e.g., error handling, result limits). It is adequate for a simple search tool but could be more complete, especially in explaining limitations or integration with sibling tools.

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 the baseline is 3. The description adds value by explicitly labeling 'query' as required and 'subreddit' as optional, and providing examples that clarify usage (e.g., global vs. subreddit search). This enhances understanding beyond the schema's basic 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 clearly states the tool searches Reddit posts and comments, specifying both global and subreddit-specific searches. It distinguishes itself from siblings like get_subreddit_posts (which likely fetches posts without search) and get_post_comments (which focuses on comments for a specific post), making the purpose specific and differentiated.

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 clear context for when to use this tool (searching across Reddit or within a subreddit) and includes examples that illustrate different scenarios. However, it does not explicitly state when not to use it or mention alternatives among sibling tools, such as using get_subreddit_posts for non-search-based retrieval.

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