reddit_hunt_leads

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'Discover', which suggests a non-mutating action, but it does not explain authentication needs, rate limits, how leads are scored or compiled, or whether this tool performs any write operations. The agent is left guessing about side effects and prerequisites.

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 zero filler. It states the core value proposition immediately and does not waste tokens on redundant details.

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?

With no output schema, no annotations, and only a one-sentence description, the agent has no information about what a returned 'lead' looks like, whether authentication is required, or what urgency threshold means in practice. The description gives a strong purpose but not enough surrounding context for confident invocation.

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 schema already documents keywords and subreddits usefully, and the tool description adds context that these are lead-hunting terms. However, min_urgency is left undocumented in both the description and schema; there is no clarification of whether urgency refers to post recency, engagement level, or another signal. Schema coverage is 67%, so the gap is noticeable but not crippling.

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 uses a specific verb and resource: 'Discover actionable freelance web scraping and browser automation leads across tech subreddits.' It clearly distinguishes this from generic siblings like reddit_search or reddit_browse_subreddit by framing it as a specialized lead-hunting tool rather than general Reddit browsing.

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 wording implies when to use it—when an agent needs freelance/automation leads from Reddit—but it does not explicitly contrast it with alternatives like reddit_search or reddit_browse_subreddit, nor state when not to use it. The use case is inferable but not directly routed.

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