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

Annotations cover the write/open-world profile, and the description adds genuinely useful context beyond them: it reaches every ticket holder at once, cannot be unsent, and requires the user's Cotlet API key. The confirmation-before-each-call note is repeated rather than enriched, but the irreversibility disclosure is valuable.

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 purpose statement is front-loaded, but the description repeats itself ('Send an operational message... Sends one message... Keep it to event information') and restates the confirmation behavior twice, adding length without new information.

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 two-parameter messaging tool with annotations and no output schema, the description covers audience scope, irreversibility, confirmation behavior, and auth requirements. It is largely complete, missing only explicit failure/precondition behavior.

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 coverage is 100%, so both parameters are fully documented in the schema itself ('Message' and 'event_id from list_events'). The description adds no syntax, length limits, or formatting detail beyond what the schema already provides, 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+resource ('Send an operational message to ticket holders') and scopes it to event info via MIO Connect, so an agent can distinguish it from list-style siblings like dice_list_ticket_holders. It doesn't explicitly name an alternative tool, but the action is 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?

Offers content guidance ('Keep it to event information such as door times') but no explicit when/when-not or sibling routing (e.g. it never points to dice_list_ticket_holders to preview recipients). Usage is implied rather than stated.

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