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

Annotations declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so safety is partly covered. The description adds real behavioral context: it is a broadcast to ALL attendees, delivered via push notification and email, requires per-call confirmation by default, and needs an API key with app access. It stops short of noting irreversibility or rate limits.

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 opening two sentences restate the same idea ('Post an announcement for the attendees of an event' / 'Posts an announcement to the attendees of one event'), and the confirmation guidance is split across two sentences. The audience and delivery facts are front-loaded, but the redundancy costs space.

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 and only two well-documented parameters, the description covers the essentials: what it does, who it reaches, the delivery channels, and the confirmation/auth requirements. It is nearly complete, missing only failure or irreversibility details.

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 both event_id and message are already documented (including 'Event ID from list_events'). The description adds no syntax or format guidance for either parameter, 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 ('Post an announcement for the attendees of an event') and clarifies the audience scope ('reaches every attendee at once'), which implicitly separates it from whova_message_speakers. It does not explicitly name that sibling, but the resource and audience are unambiguous.

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?

The description gives operational guidance about confirming each call and needing a Cotlet API key, which is useful. However, it never states when to prefer an announcement over a sibling like whova_message_speakers or whova_add_session, so the when-to-use condition is only implied.

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