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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is low, yet the description adds real behavior: stored sizes/budgets and alert clocks do not prove current price/stock/fit/delivery, the result is bounded with has_more=true signaling omissions, and it is scoped to the linked user. It also encodes output-rendering rules (Carrie/Colette attribution) that are not derivable from structured fields.

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 and usage are front-loaded well, but the latter half is a long block of persona/voice rules (Carrie's surprise, photos, seller; shop finds and near-misses belonging to Colette) that is dense and repetitive for a tool description. Much of the tail is response-formatting guidance rather than call-time 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?

With an output schema present, return values need not be explained, yet the description still usefully covers has_more and the freshness caveat. The main incompleteness is the unexplained limit parameter and the lack of clarity on default page sizing.

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%, so the description must carry parameter meaning. It clarifies the role of watch_id ('select its returned watch_id') but says nothing about limit or its 1-25 bound/relevance to has_more, leaving half the parameters undocumented.

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 first sentence gives a specific verb and resource: reading the linked user's active Hunts, their stored criteria, and historical alerts. It also states scope ('a bounded list') and distinguishes the read from the sibling mutation tool update_watch by positioning it as a pre-edit inspection.

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 explicit when-to-use conditions ('before editing an existing Hunt', 'when the user asks what Remode is watching or whether anything changed') and implies when-not by tying the read to the update flow for retrieving watch_id. The alternative path (update_watch) is effectively named by that dependency.

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