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

Beyond the destructive/open-world/idempotency annotations, it discloses that this counts against the weekly invite limit, sends real emails/push, is host-only, requires event_id, and that dry_run previews counts and blockers. These are exactly the operational risks an agent needs before invoking a destructive send tool.

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 description is front-loaded with the core action, side effects, and routing alternatives, and it is information-dense rather than padded. However, it is a long semicolon-heavy paragraph, so it is slightly harder to scan than an ideal definition.

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 destructive, open-world, non-idempotent tool with 10 parameters and no output schema, the description covers prerequisites, side effects, limits, dry-run previews, and sibling alternatives. Nothing critical for correct invocation appears missing.

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?

With 0% schema description coverage, the description carries most of the semantic burden and does well: it maps recipient_uids, distribution_list_ids, external_contacts, promo code attachment, custom message, community sending, scheduling, and dry_run. It does not spell out every field-level detail such as delivery_method enum semantics or scheduled_start_at format, so it is strong but not complete.

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?

The description states a specific verb and resource: send invitations to a live event via app, email, or both. It explicitly names the recipient categories and distinguishes this tool from sibling announcement, email, and campaign tools.

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?

It gives explicit routing guidance: use for NEW people to one event, use make_announcement for existing guests in-app, reviewed emailType announcement for event participants, and send_email_campaign for lists or newsletters. It also notes host-only access and required event_id.

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