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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value by disclosing the return shape (slug and URL) and the natural next call, which is not in any structured field.

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 sentences, front-loaded with the resource and scope, and the alternative-tool pointer lands last. The two near-paraphrased example queries cost a little density but earn their place as intent triggers.

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 carries return-format duty and does so by naming slug and URL. Annotations cover the safety profile, so the only remaining gap is result count/pagination behavior, which the limit parameter largely implies.

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 75%, with limit and country already documented and query explained. The description restates the filterable dimensions (country, city, name) but adds no syntax or format 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?

States a specific verb and resource (find CI communities) plus the discriminating detail that they 'run regular weekly jams and classes', and it separates itself from the get_* siblings by naming get_community as the detail follow-up.

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 explicit triggering user intents ('where can I dance CI in <city>', 'is there a CI jam in <city>') and points to get_community for depth. It does not, however, state when to prefer search_events or search_venues over this tool, which the sibling list makes relevant.

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