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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, etc.), the description discloses when the alert fires, how it is evaluated (after each daily baseline refresh), how it delivers (webhook and/or email), and that it is scoped to the API key. No contradiction with the annotations.

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?

The description is front-loaded and compact, with the most important action and distinction in the first sentence. A small amount of redundancy exists between 'stop polling' and the 'wake me when it matters' use-case line, but every sentence still contributes useful context.

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 4-parameter alert-setting tool with an output schema, the description provides the full behavioral contract: trigger conditions, evaluation cadence, delivery mechanisms, scope, and intended use case. Nothing essential for the agent to select and invoke the tool correctly is missing.

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?

The schema already documents all four parameters (100% coverage), so the baseline is 3. The description adds the key relationship between parameters — the OR condition between percentile_below and delta_below — and clarifies the saved-shortlist source, but it largely restates examples already in the schema.

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 opens with a specific verb and object, 'Set a DRIFT ALERT on a saved shortlist,' and clarifies the monitoring scope ('national standing moves materially'). It also names the exact trigger conditions and the resource type (a saved shortlist), which distinguishes it from the sibling site/market alert tools.

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 usage context: the alert is for stopping polling, acting as a 'wake me when it matters' loop for long-running siting campaigns, and is scoped to a saved shortlist. It does not explicitly name set_site_alert or set_market_alert as alternatives or state when not to use them, so it falls 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.