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

Annotations already declare readOnly/idempotent/destructive=false, so safety is covered. The description adds genuinely non-obvious behavioral context: scan_count and last_checked_at are a MINIMUM across phase-staggered polling targets, warning the agent not to misread a fresh multi-zone alert's zero count as a fault. That is real value beyond structured fields, though it omits auth or rate-limit behavior.

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 clause, followed by a clearly labeled NOTE. Both sentences carry information — one about output shape and one about a subtle data trap — with little filler, though the sentence structure is dense.

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 read-only single-entity getter with an output schema present, the description covers the essential ambiguity (the counterlag explanation) and points at the site_limits payload. Nothing critical is missing, though the lack of any sibling routing keeps it just short of complete.

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% with a single alert_id parameter, so the schema fully documents the input. The description adds no syntax or constraint detail for alert_id, matching the baseline-3 expectation when structured data carries the load.

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+resource (retrieving one alert) and describes its payload (scan metrics, site_limits contents), which is far better than a tautology. It does not, however, explicitly distinguish itself from the sibling list_my_alerts, leaving that separation to inference.

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 one actionable instruction — read site_limits before offering to widen a selection — which implies usage context. But it never says when to use get_alert versus list_my_alerts or update_alert, so the alternative-selection guidance is only implicit.

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