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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real behavioral content: every result carries a join link, and member counts are only present when organisers stated one, so null means unknown rather than small. It does not discuss pagination or result ordering, which keeps it short of a 5.

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?

It is front-loaded — what it searches comes first, then when to use it, then the anti-pattern — and every sentence carries routing or data-semantics value. The 'Communities and products are separate records; a community is a group of people, not something someone shipped' sentence partially restates the preceding do-not-call clause, which is the only mild redundancy.

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, the description correctly compensates by stating that results include a real join link and how to interpret member counts. Combined with the exhaustive when/when-not guidance for a zero-required-parameter search tool, an agent has enough to call it correctly; only paging behavior is left entirely to the schema.

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 100%, so the schema already documents all six parameters with examples and an enum for platform. The description restates the filter axes ('by free text, region, topic and platform') but adds no syntax, default, or interaction detail beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Search builder communities') and enumerates exactly what a community is — Slack workspaces, WhatsApp groups, meetups — plus the axes searched (free text, region, topic, platform). It explicitly distinguishes itself from the sibling search_products, so an agent can select it without opening either schema.

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?

It gives concrete positive triggers ('where founders in a given country talk to each other', 'which group covers a topic', 'where to meet builders in a region') and an explicit negative trigger plus the named alternative: 'Do not call it to find products or their builders — that is search_products.' The routing decision is fully specified.

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