Free lookup of a subreddit's promotion posture from Thread Otter's community vetting data (2,000+ profiled subreddits): self-promo policy, link policy, and how to write for the room.
| Name | Required | Description | Default |
|---|---|---|---|
| subreddit | Yes | Subreddit name, e.g. "startups" or "r/SaaS". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It discloses the data source (Thread Otter's vetting data, 2,000+ subreddits), that it is free, and the kind of content returned. However, it does not mention what happens for unprofiled subreddits or potential data staleness, leaving some edge cases undocumented.
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, economical sentence with a clear lead-in ('Free lookup') followed by a colon and specific output types. Every phrase earns its place, and there is no verbose repetition of schema information.
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?
For a simple one-parameter lookup tool without an output schema, the description sufficiently explains what the tool does and what it returns. It covers the key output categories (self-promo, link policy, writing style) but does not specify behavior for missing or niche subreddits. Overall, it is complete enough for the tool's simplicity.
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 already fully documents the single parameter 'subreddit' with an example. The description adds no additional parameter-specific semantics beyond what the schema provides. Baseline 3 is appropriate since schema coverage is 100%.
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 a specific action ('lookup') and a specific resource ('a subreddit's promotion posture'), and enumerates what it returns (self-promo policy, link policy, how to write for the room). This distinguishes it from sibling tools like find_buyer_threads or get_demo_report, which serve different purposes.
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 communicates a clear use case: quickly look up a subreddit's rules before posting. It does not explicitly mention alternatives or when not to use it, but the sibling tools are distinct enough that the intended context is clear. It provides context (free lookup, data source) but lacks exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools (competitor_complaints, demand_radar, reddit_demand_board, find_buyer_threads) all mine Reddit threads for demand, complaints, or buyer interest, with overlapping purposes that could easily confuse an agent. The boundaries are unclear, especially between demand_radar and reddit_demand_board, which both offer weekly demand overviews.
All names use snake_case and are readable, but the pattern is mixed: some are verb-first (find_buyer_threads, get_demo_report, get_started) while others are noun-heavy phrases (competitor_complaints, reddit_demand_board, subreddit_rules). This inconsistency makes the set feel less predictable.
With 7 tools, the set is well-scoped for a focused Reddit market research server. Each tool serves a distinct function within the domain, and none feel redundant or excessive.
The tool set covers the core workflows: discovering demand, finding buyer threads, checking competitor complaints, and understanding community rules. Minor gaps include lack of direct keyword search or alerting, but agents can chain existing tools to achieve most goals.