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

Annotations already flag this as destructive, non-read-only and open-world, and the description adds real context beyond them: wholesale replacement of entities/notifications, the fact that filter objects replace rather than merge, ZDR exclusion, kind-dependent unprocessable_entity errors, and email verification gating. However, it never states what the response looks like or whether the caller can see prior values before overwriting a set — gaps that matter for a destructiveHint mutation.

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?

Well front-loaded, but long and partly redundant: the filters paragraph restates the speaker_roles / speaker_statement_characteristics restrictions that already appear verbatim in the schema descriptions. The delivery/verification paragraph repeats the `notifications` param description. Tightening would preserve meaning with less duplication.

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?

Covers the tricky parts an agent needs for a 10-param destructive mutation with nested objects: replacement semantics, kind constraints, pause semantics, filter clearing, and error conditions. Missing only the return shape (no output schema exists) and whether alert_id is org-scoped, which keeps it from a 5.

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 already 100%, so the baseline is 3; the description earns extra credit by adding cross-parameter semantics the schema cannot express — keyword vs entities mutual exclusivity by alert kind, {} clearing filters, and is_active meaning pause/resume rather than delete. It does repeat a fair amount of the schema's own enum/filter prose, which caps it below 5.

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?

Opens with a specific verb+resource ('Update an existing alert') and immediately clarifies the lifecycle boundary against particle_alert_create ('an alert's kind is fixed at creation — to change it, create a new alert'). An agent can distinguish update from create/delete/get/list without consulting any schema.

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?

Explicitly states partial-update semantics ('Only the fields you pass change'), which params replace wholesale, and the kind-specific rule that KEYWORD_MENTION takes `keyword` while entity alerts take `entities`. It also routes the agent to particle_alert_create for kind changes and names resolve tools for slugs.

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