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

Annotations already cover non-readonly/non-idempotent behavior; the description adds substantial context beyond them: each call creates a new watchlist, plan-based count limits, Free-plan daily digest vs Pro webhook, signed HTTPS delivery, and rejection of filters that match everything.

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 core purpose is front-loaded in the opening clause, and the remaining sentences carry plan, delivery, and lifecycle constraints rather than filler. The dense semicolon-heavy style is slightly harder to scan but nothing is wasted.

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?

Given an output schema and full annotation coverage, the description still supplies the operational context an agent needs: creation semantics, plan limits, alert delivery channels, and where to manage existing watchlists. Nothing material 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?

Schema coverage is 100%, so the schema already documents parameters thoroughly. The description still adds value by tying `filters` to the search_tenders semantics and explaining channel plan constraints (webhook requires Pro, email default on Free).

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 ('Save a query and filters as a watchlist') plus the downstream effect (ongoing monitoring, email/webhook alerts) and return value (watchlistId, current match count). This clearly distinguishes it from search_tenders, which is a one-off query tool.

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?

Frames the tool around 'ongoing monitoring' versus a one-time search, notes per-plan watchlist limits, and routes management/deletion to the dashboard. It stops short of an explicit 'use search_tenders instead when you just need results now' statement, but the context is clear.

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