search_reddit_query

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

With no annotations, the description carries the full burden. It communicates the basic read-only nature of the operation ('Search') and hints at the mechanism ('through the search page'), but it does not disclose pagination behavior, rate limits, output format characteristics, or any unusual constraints.

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 filler. It is appropriately concise for a simple search operation, though it could be slightly expanded to clarify scope and alternatives without becoming bloated.

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 is too sparse to be fully contextually complete. It does not address the existence of the closely related sibling 'search_reddit', nor does it mention any practical constraints or expected behavior. The output schema covers return values, but the description still leaves important selection and invocation context unresolved.

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 input schema fully documents all five parameters. The description adds nothing beyond the obvious keyword-based purpose, which is appropriate given the schema already provides detailed semantic explanations for every parameter.

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 identifies the action ('Search Reddit') and specifies the input type ('by keywords') and mechanism ('through the search page'). It is not a tautology and conveys the core purpose. However, it does not differentiate this tool from its sibling 'search_reddit', which likely serves a similar role.

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 no guidance about when to use this tool versus 'search_reddit' or any other sibling. It does not state any exclusions, conditions, or preferred contexts, leaving the agent to guess which of the two search-related tools to invoke.

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