search_reddit

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

With no annotations, the description carries the full burden, and it does well by disclosing the non-obvious search limitation: 'Reddit's own search covers post titles and bodies, not comment text.' It also states what is returned ('matching posts and their text') and routes comment reading to get_post. It does not mention auth or rate limits, but for a read-only search tool the added context is substantial.

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 front-loaded with purpose and usage, includes only the essential caveat about comment search coverage, and closes with a compact Args block. Every sentence adds value; there is no filler or unnecessary repetition.

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?

The description covers when to use the tool, parameter semantics, return value ('matching posts and their text'), and an important behavioral limitation. Because there is no output schema, it would be even stronger with explicit result metadata or pagination details, but it is already enough for an agent to call the tool correctly.

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?

The input schema has 0% description coverage and no enum definitions, but the description fully compensates by listing all five parameters with concrete allowed values: sort options, time_filter options, limit range 1-100, subreddit 'r/' flexibility, and query meaning. This gives an agent everything needed to construct valid arguments.

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 a specific action and resource: 'Search Reddit discussions for real user opinions and experiences on a topic.' This clearly distinguishes it from a generic search tool, though it does not explicitly contrast with the sibling browse_subreddit, so sibling differentiation is incomplete.

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 provides explicit selection context: 'Use this when the answer depends on what people who actually used or did the thing report: hands-on impressions...' This tells an agent when to choose it. It mentions get_post for following up but does not give an explicit when-not-to-use or direct alternative comparison with browse_subreddit.

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