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

The description explains the non-obvious side effect that justifies readOnlyHint=false and idempotentHint=false: reading marks alerts delivered unless peek=true, and it defines what an empty result means. It doesn't cover pagination, whether delivery marks are permanent, or per-account scope, so it isn't exhaustive.

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?

Front-loaded with the core purpose and ordering, then the behavioral caveat and empty-result semantics. The list of alert categories is long but informative rather than redundant; size is appropriate for carrying side-effect information annotations don't state.

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, 4 optional parameters, and 25% schema coverage, the description carries a lot of burden. It covers the consumption semantics and empty-state meaning well, but an agent still lacks limit/status behavior and pagination guidance needed to invoke it optimally.

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 only 25% (just 'watchlist'), so the schema documents almost nothing. The description adds real meaning for peek (reading consumes alerts; peek avoids that) and implied semantics for an empty result, but says nothing about limit (max 100) or the pending/all status enum, leaving half the parameters unexplained anywhere.

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 ('New alerts for this account's watchlists'), gives the ordering ('highest priority first'), and enumerates the alert categories covered. It clearly covers the alert-listing niche, though it never names which sibling (e.g., get_regulatory_deadlines) is the alternative for non-alert views.

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 usage context ('New alerts', 'An empty list means nothing new') and warns that reading consumes the alerts unless peek=true, which is genuinely useful selection guidance. But it never says when to prefer this tool over siblings like get_regulatory_deadlines or rate_regulatory_alert, and there are no explicit exclusions.

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