discover_communities

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

No annotations are provided, so the description carries the full behavioral burden. It implies a safe read ('Search') but says nothing about external network calls, rate limits, permissions, result caching, or whether results are deduplicated or ranked. For a discovery/aggregation tool this is a meaningful gap.

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?

A single efficient sentence with the verb and resource front-loaded and no filler. Nothing needs trimming and the core scope is immediately visible.

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 search-style tool with an output schema (so return values need not be explained) and no annotations, the description covers the 'what' adequately. It falls short on workflow placement and parameter meaning, making it minimum-viable rather than 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?

Schema description coverage is 0%, so the description must compensate. It hints that 'query' is an audience or domain and that 'source' may take values like subreddit, GitHub repo, or forum, but never states this explicitly and says nothing at all about the 'limit' parameter or any accepted value formats.

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 gives a specific verb ('Search') and a concrete resource set (communities, subreddits, GitHub repos, forums), scoped to an audience or domain. It is distinguishable from siblings like find_audiences and discover_competitors by resource type, though it never names an alternative to route against.

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?

There is no when-to-use or when-not-to-use guidance. The description does not say whether this should run before or after find_audiences, discover_competitors, or search_source, leaving the agent to infer placement in the research workflow entirely on its own.

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