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

Annotations only declare the write/openWorld safety profile; the description adds genuinely useful behavior: the message goes out under the user's name, the recipient scope is limited to opted-in members, the return value is a reach count, and the user's Cotlet API key is required. It stops short of discussing reversibility or delivery constraints, but adds real context beyond the annotations.

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 purpose is stated twice in near-identical wording ('Contact members of your group who opted in...' vs 'Sends one message to the members of your group who opted in...'), which is wasteful. The latter half (returns count, confirmation, API key) is well front-loaded and earns its place.

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 an outbound-messaging tool with no output schema, the description covers return value (count of people reached), the auth requirement, and the confirmation policy — the key things an agent needs. It lacks detail on failures or recipient limits, but is otherwise sufficient to call 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?

Schema description coverage is 100% (body, subject, group_urlname all documented), so the schema already carries parameter meaning. The description adds no syntax, format, or constraint details for the three params, 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 (sends/contact), resource (members of your group), and a precise scope qualifier (who opted in to organizer announcements). This distinguishes it from the sibling meetup_message_attendees, which targets event attendees, without needing to open a 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 clear operational context: you confirm each call by default and can disable that, and it explicitly requires confirming with the user before each call because it reaches other people. It does not name a sibling alternative for messaging a different audience, so it stops short of a full when/when-not comparison.

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