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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower. The description adds real value beyond them by explicitly stating that this call triggers no evaluation, delivery, subscription or destination lookup, which reassures an agent about side effects. It stops short of describing pagination behavior or result ordering.

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?

Two sentences, front-loaded with the core action and followed by the most decision-relevant caveat. No filler, though 'recorded diagnostic applicability' is jargon that adds ambiguity more than information.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The remaining gap is pagination mechanics for limit/cursor, which the description only gestures at.

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 0% for both parameters, so the description carries the burden. 'Page' hints at pagination, but neither the limit (default 25, max 50) nor the cursor token is explained in the description, leaving the agent to reverse-engineer them from the raw JSON schema constraints.

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 (page/list) and resource (saved alert rules), plus a secondary resource (recorded diagnostic applicability). It reads clearly as the list counterpart to the sibling get_alert, though it does not explicitly name that sibling.

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?

Usage is implied by 'Page your saved alert rules', but there is no explicit when-to-use versus get_alert or compare_pools, and no statement of prerequisites. The negative clause ('No evaluation, delivery... is triggered') is useful side-effect guidance rather than selection guidance.

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