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

With no annotations provided, the description carries the full burden. It transparently discloses the multi-step process (crawl, buyer identification, Reddit mining), the async nature (results ready in ~2-3 minutes via get_demo_report), and a rate limit (2 runs/day). This is comprehensive for a demo tool, covering both behavior and constraints.

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 three sentences, each earning its place: the first explains the core function, the second covers output and timing, and the third states the limitation. No fluff, front-loaded with the most important context (free GTM demo) and easy to parse.

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?

Despite having no output schema, the description explains what the return looks like (report link) and how to get results (via get_demo_report). It also conveys the tool's role within a broader workflow (GTM demo) and mentions the rate limit, making it complete for the tool's complexity and context.

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 has 100% coverage for both parameters (website_url and email), with clear descriptions. The tool description reinforces the website_url role ('give it a product website URL') but does not add substantial new semantics beyond the schema. Baseline 3 is appropriate given the high schema coverage and marginal added value.

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's function: provide a product website URL, Thread Otter crawls the site, identifies buyer personas, and mines relevant Reddit threads. It uses specific verbs ('crawls', 'mines') and the resource (Reddit threads, website URL), which distinguishes it from sibling tools like get_demo_report (retrieval) and reddit_demand_board (likely similar but not same workflow).

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 frames this as a 'free GTM demo' and gives a clear workflow: call this tool, then use get_demo_report after 2-3 minutes. It also notes the 2-runs-per-day limit, which sets usage expectations. However, it doesn't explicitly contrast with alternatives like reddit_demand_board or subreddit_rules, so it falls just short of full guidance.

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