search_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 does add genuinely useful non-obvious context — the upstream data source and the CC-BY-4.0 attribution requirement — but says nothing about result shape, pagination, or rate limiting. For a read/search tool the safety profile is self-evident, so the attribution detail earns partial credit.

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?

Three short, front-loaded fragments with no filler; the resource leads and ancillary licensing info trails. The endpoint URL and license note are arguably not needed for tool selection, but they cost little.

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 an eight-parameter tool with no output schema, the description documents the domain but not what a result looks like or how result volume is bounded beyond the schema's limit field. It is adequate for selection but thin on operational 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?

Schema description coverage is 100%, so all eight parameters (q, size, type, focus, limit, location, platform, activityLevel) are already documented with their matching semantics. The description adds no filter syntax or format detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 the resource domain (AI safety communities, groups, meetups) and points at a specific API endpoint, so the agent can infer this is a query over community data. However, it never states an explicit verb like 'search' or 'filter', and with ten sibling search_* tools it makes no attempt to distinguish itself beyond the resource noun. Purpose is inferable but under-specified.

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 guidance on when to use this tool versus siblings like search_organizations or search_events, and no mention of prerequisites or exclusions. The only implied usage is that the tool concerns communities, which the resource noun already conveys.

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