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

Annotations already cover read-only, idempotent, open-world behavior, so the description's job is to add output-shape context — and it does, naming the exact fields returned (title, time, URL, status, hosting group) and explicitly excluding attendee/RSVP lists. It also discloses the automatic geocoding side effect of `city`. No pagination or geocoding-failure behavior is described.

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?

Two sentences: the first covers what is searched and returned, the second the location-input constraint. Nothing is redundant or buried; the critical scoping detail is front-loaded.

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-value disclosure and does so adequately by enumerating the returned fields. For a 6-param open-world search, remaining gaps (result ordering, empty-result behavior, geocoding failure) are minor rather than blocking.

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 every parameter is already documented, including 'Use instead of `city`' on lat/lon. The description restates the either/or location rule in one convenient place but adds no new syntax, ranges, or defaults beyond the schema. 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?

Opens with a specific verb+resource+scope: 'Search Meetup for upcoming public events by keyword, near a city or a lat/lon point.' That clearly separates it from the fetch-by-id siblings (meetup_event, meetup_group, meetup_group_events), though it never names them explicitly.

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 states the location-input choice ('Provide either `city` or `lat`+`lon`') and rules out attendee/RSVP data, but gives no guidance on when to use this search versus the sibling event/group tools. Usage is implied by the verb 'search' rather than spelled out.

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