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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the description adds real value: messages go out from Whova rather than the user's own address, they reach other people, confirmation is on by default but can be disabled, and an authorized API key is required. It does not cover irreversibility or rate limits, keeping it at 4 rather than 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?

The scope rule is front-loaded and the confirmation and auth constraints are attached to the action they modify. The second sentence ('Sends an email to speakers through Whova's speaker messaging') largely repeats the opening, which is the only real waste.

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 4-param outbound-messaging tool with annotations and no output schema, the description covers targeting, delivery channel, confirmation, and auth requirements. It omits nothing critical, though it could say whether the send can be undone or what the response confirms.

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 the schema already documents event_id, subject, body and speaker_ids. The description's note that omitting speaker_ids emails all speakers just restates the schema's 'Default: all speakers' and adds no format or syntax detail.

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 ('Email all speakers of an event, or the ones you list, through Whova') plus the targeting scope, so the action is unambiguous. It does not name or contrast with the sibling whova_send_announcement, which is the nearest alternative, so it falls short of 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?

Gives a clear selection rule ('Leave speaker_ids out to email all speakers of the event') and an operational prerequisite ('Needs the user's Cotlet API key with access to this app'). It also states the confirmation policy in detail. It never mentions when to prefer this over whova_send_announcement, so it stops short of explicit alternatives.

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