Research a topic on Reddit

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

The description adds rich behavioral detail beyond the readOnly/openWorld annotations: it discovers subreddits when none are given, ranks by discussion depth rather than upvotes, pulls comments from winning threads, and returns permalinks. This accurately previews the tool's behavior without contradicting the 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 is tightly written in four sentences with no wasted words. It front-loads the core action, then efficiently covers workflow, output guarantees, and a practical usage tip.

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 7 parameters, no output schema, and a multi-step orchestration, the description is largely complete: it covers workflow, key output clues (evidence, permalinks, thread rankings), and usage strategy. It stops short of describing a concrete return structure, but the schema and annotations carry much of the remaining burden.

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 meaning beyond the schema by explaining that subreddits can be omitted for automatic discovery and that includeComments=false provides a cheap overview before committing context. This semantic context raises the score above baseline.

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 states a specific verb and resource: "Run a full Reddit research pass and return the evidence." It clearly differentiates itself from sibling tools by describing the orchestration flow (discover subreddits, search, rank, pull comments) and positioning itself as the first-stop research tool.

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 says "This is the tool to reach for first," giving strong when-to-use guidance. It also advises setting includeComments false for a cheap overview before committing context. However, it does not explicitly name sibling alternatives or state when to prefer them, so it is not a full 5.

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