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

Goes well beyond the annotations: it discloses a recurring daily re-run, email delivery to the key's account, the exact alert thresholds, the auth requirement with a connect URL, and a pricing/quota model (first alert free, more are Pro). It stays silent on the non-idempotent behavior declared in annotations — an agent isn't warned that repeat calls may create duplicate alerts.

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 trigger criteria; the auth and pricing clauses are compact and relevant to whether the agent should call it. Slightly dense with commercial detail that a model may not need.

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 annotations covering the mutation/safety profile and no output schema, the description supplies the missing pieces an agent needs: prerequisite (finished search + key), side effect (daily email), and trigger conditions. The main remaining gap is duplicate-alert/idempotency behavior and how to stop an alert.

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 0%, so the description carries the burden for the single searchId parameter. It adds some meaning by stating the search must be a *finished* search, but doesn't clarify the s_ prefixed ID format or what happens if the ID refers to an unfinished search.

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 ('Starts the otter's daily re-run of a finished search') plus the exact trigger conditions for the alert (5% or $50 drop, cheapest pick disappears). Strong on what it does, but it never names the closely related siblings (watch_booking, watch_similar_homes, watch_booking) that an agent would have to choose between.

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 implies the precondition that the search must already be 'finished' and that a key is required, which guides invocation. But it gives no explicit when-to-use/when-not guidance and does not contrast itself with watch_booking or watch_similar_homes, which are the obvious alternatives for watching prices.

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