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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description adds value by disclosing the return shape: each row carries alert_type, a policy field (per_event, cooldown, hysteresis) and a type-specific hl or pm object. Pagination/limits are not mentioned, which is the only notable gap.

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 front-loaded sentences: purpose, then default/override behavior, then the workflow use and return shape. Dense and largely waste-free, though the final sentence packs several field definitions into one long clause that is harder 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?

With no output schema, the description usefully sketches the row structure and type-specific nested objects, and the single optional parameter is covered. Missing only volume/limit expectations for an unbounded list of a user's alert rules.

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% and the single parameter already documents its default and meaning. The description restates the same semantics (default active, include paused/deleted) without adding format or edge-case detail beyond the schema, 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 and resource ("List the current user's alert rules") with explicit scope. It separates this from the mutation siblings by noting it's the way to obtain an alert_id before editing or deleting, and from alerts_events implicitly by dealing in rules rather than notifications.

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?

Gives a clear default (active alerts only) and the switch (include_inactive=true) for paused/deleted ones, plus an explicit workflow use case: look up an alert_id before editing or deleting. It does not explicitly say when to prefer alerts_events or alerts_list_channels instead, so no full alternative routing.

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