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

Annotations already flag destructiveHint=true, openWorldHint=true and non-idempotent, but the description adds genuinely new behavior: a hard quota (10 per event) and an asynchronous gate (waits for owner's approval) that means the call does not fire immediately. That approval/rate-limit context is exactly what annotations cannot express. It still doesn't say what happens if the quota is exhausted or what the caller observes while pending.

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?

Three short sentences, front-loaded with the core action, then the quota, then the approval gate. Every sentence carries information an agent needs and there is no filler.

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 non-idempotent, destructive broadcast with no output schema, the description supplies the critical operational facts (quota, human approval) and the recipient targeting. Only edge behavior — quota-exceeded errors and the post-approval outcome — is left unstated, which is a minor gap.

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 event_id, message, statuses and show_on_event_page are already documented, including the enum values. The description only echoes the status filtering ('by RSVP status') and adds nothing about message length limits or the show_on_event_page default. Baseline 3 for a fully documented schema.

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 (text/send) plus resource (message to guests) and a scoping filter (RSVP status), which separates it from invite_guests and approve_guests. It doesn't explicitly name a sibling alternative, so it stops 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?

The description makes the use case clear (broadcast texting segmented by RSVP status) and adds two decision-relevant constraints: the 10-blast-per-event cap and the owner approval requirement. It does not say when to prefer another channel or tool instead, so no exclusions are provided.

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