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

Annotations declare this is a non-read-only, open-world write but say nothing more. The description adds substantial behavior: a 2,000-character limit, no attachments, default per-call confirmation that can be disabled, an explicit warning that it reaches other people, and the API-key requirement. That is meaningful disclosure beyond the structured fields.

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?

Purpose is front-loaded in the first sentence, followed by mechanism, limits, and safety/auth notes. The confirmation point is stated twice ('By default you confirm each call' and 'confirm with the user before each call'), a mild redundancy, but overall it is efficient and easy to scan.

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 mutation tool with no output schema and open-world behavior, the description covers constraints, auth, and the confirm-before-sending requirement, which is what an agent needs. It lacks any mention of what a successful send returns or how many recipients it may reach, but the essentials are present.

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, message, subject, statuses, tags, and the template enum. The description reinforces how statuses and tags select recipients and that template can be custom, but adds no syntax or format detail beyond the schema, 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: it sends a broadcast to guests, selected by status and optional Guest Tags, with a template or custom text. The mechanism is clearly described, but it never names or contrasts against the close sibling paperless-post_send_private_message, leaving the agent to infer the broadcast-vs-individual distinction.

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 clear operational context: sending a broadcast 'like the Messages & Reminders screen,' and that recipients are chosen by status/tag. It also says confirmations default on but can be switched off, and advises confirming with the user. No explicit when-not-to-use or sibling alternative is given, so it stops short of a 5.

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