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

Annotations cover the safety profile (write, non-destructive, open-world), and the description adds meaningful context beyond them: it returns a reach count, defaults to per-call confirmation that can be switched off, and requires a Cotlet API key with app access. That is strong added value, though it omits rate limits or message-length constraints.

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?

The core statement is repeated almost verbatim in the first two sentences ('send a message to the people who RSVPed going to an upcoming or past event' vs 'sends one message with a subject to the people who RSVPed going to an upcoming or past event'). Confirmation behavior is also stated twice, diluting a definition that could be tighter.

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 no-output-schema write tool, the description covers the return signal (reach count), confirmation policy, and auth requirement, which is enough for an agent to call it correctly. Only marginal gaps remain (no message-size or delivery caveats).

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 event_id, subject and body are already documented (event_id explicitly points to list_events). The description mentions subject but adds no format, length, or constraint details beyond the schema, so 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: send a message to people who RSVPed going to an event, scoped to upcoming or past events. The RSVP/attendee scoping implicitly distinguishes it from the sibling meetup_message_members, but no sibling is named explicitly, so it falls short of a 5.

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?

Offers behavioral guidance ('confirm with the user before each call') rather than selection guidance. It never states when to choose this over meetup_message_members or meetup_announce_event, so usage is only implied.

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