Search Reddit

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

The annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by noting that results are top-ranked, specifying the compact JSON output format, and indicating credit cost (~1 ScrapeCreators credit). This enhances transparency beyond the schema/annotations.

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 consists of two concise sentences: the first states the tool's action and primary use case, the second details output and credit usage. Every sentence is necessary and front-loaded with critical information (resource path, purpose). No wasted words.

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 the tool's simplicity, presence of output schema, and annotations, the description adequately covers return structure, credit cost, and use case. It omits minor details like error handling or pagination beyond the limit parameter, but these are not critical for a basic search tool.

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?

Input schema has 100% coverage with clear descriptions for both parameters (query, limit). The description does not add any additional semantic detail beyond what the schema already provides. Baseline 3 is appropriate.

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 it performs a Reddit keyword search, specifies the endpoint and ranking, and identifies the use case (mining customer language for ad hooks). It distinguishes from sibling search tools by targeting Reddit specifically.

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 explicitly mentions when to use this tool (to mine customer language from Reddit for ad copy). However, it does not provide explicit when-not-to-use guidance or directly compare with alternatives like search_google_ads or search_threads, though the name and context imply platform-specific usage.

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