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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the description is not burdened with the safety profile. It does add genuinely new behavioral facts: the result shape is slug and URL only, and address/events are deliberately absent and require a follow-up get_venue call. It stops short of describing pagination or the 1-20 limit's effect on response size.

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 what the tool finds before the usage trigger and the follow-up routing. Every clause carries information an agent needs to pick and sequence the call.

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 compensates by stating what is returned (slug and URL) and where the rest lives (get_venue). Working alongside annotations that cover the safety profile, it leaves no gap an agent needs filled to invoke it correctly.

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 schema describes three of four parameters (country, query, limit) but leaves city bare at 75% coverage; the description supplies the search axes 'by name, country or city', which maps query/country/city to intent. It adds meaning beyond the schema but does not clarify matching behavior (exact vs fuzzy) for city.

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?

States a specific verb and resource domain ('Find dance studios and retreat centers that host Contact Improvisation classes, jams and events') and names the lookup axes (name, country, city). It is clearly separable from search_communities, search_events and get_venue without opening any 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?

Gives an explicit situational trigger ('where is CI taught in <city>'), names the complementary sibling to run alongside it (search_communities), and routes the agent to get_venue when address/upcoming-event detail is needed. That is when-to-use plus alternatives, not just implied context.

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