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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), so the description adds the useful extras: per-status ordering rules, the fields each item carries (going/waitlist counts, attendee limit), and an auth requirement (Cotlet API key with access to the app). It does not describe pagination behavior despite the cursor param, so not a 5.

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?

Four short, front-loaded sentences that lead with the resource and scope. The "going and waitlist counts" sentence mildly overlaps the earlier "RSVP counts," but the auth note and get_event pointer each carry weight.

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 a read-only list tool with no output schema, the description covers what is returned (counts, limit, status), ordering, and the auth prerequisite, so an agent has enough to call it correctly. Minor gaps (pagination semantics, total counts) remain but are non-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 (limit, cursor, status enum, group_urlname) is already documented in the schema. The description adds no syntax or format detail beyond the structured fields, 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?

States a specific verb+resource ("Lists events of one group") with scope (one group, soonest first / newest first by status) and explicitly distinguishes itself from meetup_get_event, which "returns the full text." An agent can separate it from the sibling getter without opening either 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 a clear usage context (list a group's events, ordered by upcoming vs past) and routes to get_event for full text. It stops short of explaining the status enum trade-offs (draft/cancelled) or when to prefer listing per status, so it is clear context without full exclusion guidance.

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