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 full burden. It discloses that this is a free lookup from Thread Otter's community vetting data, noting the 2,000+ profiled subreddits and implying limited coverage. It doesn't detail error handling for missing subreddits or rate limits, but 'free lookup' conveys read-only behavior.
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, well-structured sentence that front-loads the core purpose ('Free lookup of a subreddit's promotion posture') and includes valuable details about the data source and output content without any filler.
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, the description covers the essential context: what it does, the data source, coverage scope, and the type of information returned. It lacks explicit fallback behavior for unavailable subreddits, but given the simplicity, it is largely complete.
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 provides a clear description and example for the 'subreddit' parameter. The tool description adds no additional parameter details, but since schema coverage is 100%, the baseline of 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 the tool does a 'free lookup' of a subreddit's 'promotion posture', specifying the exact data returned (self-promo policy, link policy, how to write for the room). This distinct function is well separated from sibling tools like find_buyer_threads or reddit_demand_board.
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 makes it clear the tool is for looking up subreddit promotion rules before posting. It provides a clear context but does not explicitly mention alternatives or when not to use it, so it falls short of a 5.
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.
Each tool serves a clearly distinct function: find_buyer_threads starts a search, get_demo_report retrieves results, reddit_demand_board shows trends, subreddit_rules provides policy info, and get_started offers guidance. The related pair of find/get is complementary rather than overlapping, so an agent would not mix them up.
Tool names follow a loose verb_noun pattern for find_buyer_threads, get_demo_report, and get_started, but reddit_demand_board and subreddit_rules are noun phrases. This mixed style is readable but not fully consistent with a single convention.
With 5 tools, the server is well-scoped for its purpose of Reddit demand research and community vetting. Each tool covers a distinct aspect without unnecessary bloat, making it easy for an agent to navigate.
The tool set covers the full workflow: initiating a buyer-thread search, fetching the report, exploring broader demand trends, checking subreddit rules, and getting started. No critical operations are missing for the advertised functionality.