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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful behavior the schema cannot: it returns communities with slug and URL, and points to get_community for full details. It does not state pagination/limit behavior, but that is minor.

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 sentences, front-loaded with the core purpose, followed by a concrete query example and the return/hand-off note. Every sentence earns its place with no 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?

With no output schema, the description steps in to describe the return shape (slug and URL) and the natural next call (get_community). Annotations cover the safety profile, so the only residual gap is the undocumented city parameter and limit/pagination nuance, which the schema mostly handles.

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 coverage is 75% (city is undocumented in the schema). The description compensates by naming the filter dimensions — 'by country, city or name' — which maps country/city/query, and its examples clarify that query covers name-or-description matching. Adds meaning beyond the schema for the loosely documented inputs.

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?

Specific verb (find/search) plus a precisely scoped resource ('local Contact Improvisation communities, the groups that run regular weekly jams and classes') with the filter dimensions named. It distinguishes itself from the get_* siblings by stating it returns the list and routing detail lookups to get_community.

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?

Explicitly frames itself as 'the primary tool' for 'where can I dance CI in <city>' and 'is there a CI jam in <city>', and names get_community as the follow-up for details. No exclusions against search_events/search_venues, but the core when-to-use is clear.

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