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

Annotations only declare readOnlyHint=false, idempotentHint=true and destructiveHint=false. The description adds real behavior: an email is actually sent on trigger, duplicate handling ("one watch per email per product; calling again updates the target" — the semantic behind idempotentHint), and alert payload (product link + unsubscribe). It doesn't cover delivery timing, rate limits, or failure modes.

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?

Four dense sentences, front-loaded with the trigger and the usage condition, then the duplicate/update semantics, then the alert contents. Every sentence carries distinct information with no padding.

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 compensates by describing what the alert contains (product page link, unsubscribe link) and what re-calling does. It omits what a successful call returns to the agent (confirmation/ID), which is the only meaningful gap for a 3-parameter mutation tool.

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%, so the schema already documents slug, email and target_price, including the omit-to-use-verified-low behavior. The description reinforces email provenance ("never invent or reuse one") but adds no new syntactic or format detail beyond the schema — baseline 3.

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+resource ("Email the user when a product is at a good price... or at or under a target price") with the trigger condition spelled out. It also names the sibling tools (search_catalog/get_product) as prerequisites, so the agent can place it in the workflow without opening a 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?

"Use after search_catalog/get_product when the user wants to be told when to buy" gives explicit sequencing and intent, and "Ask the user for their email; never invent or reuse one" is a concrete precondition. It stops short of naming when NOT to use it (e.g. one-off price checks), so it is not fully exhaustive.

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