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

Annotations declare readOnlyHint=false and idempotentHint=false, and the description explains why: returned alerts are marked as read, which is a real state mutation beyond what the annotation flags convey. It also discloses a rate limit ('limited per hour') on refresh. It stops short of covering auth needs, ordering, or pagination, so it is strong but not 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?

Four tight sentences, front-loaded with what is returned before the refresh hint and the empty-list caveat. Every sentence adds information an agent needs; there is no filler or restatement of the title.

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 does the right thing by characterizing the returned payload (alerts about new events and changes) and the empty-list case. It also flags the read-marking side effect. Missing details are the shape/order of alert objects and defaults for limit/include_seen, which leaves a small gap for a 3-param 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 description coverage is 0% for three parameters, so the description must carry the load. It explains refresh (run a check now, rate-limited) but says nothing about limit or include_seen, whose semantics (whether already-read alerts are returned, defaults) are genuinely ambiguous. Two of three parameters remain undocumented in both schema and prose.

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 description gives a specific verb (return) and a well-scoped resource: newly observed events matching a watchlist or followed artist, plus changes (cancelled, postponed, rescheduled, price/venue/time changes) to matching or saved events. It is much clearer than a generic 'list alerts', but it never names or contrasts any sibling (e.g. get_event_changes, manage_event_watchlist), so an agent must infer the boundary.

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?

Usage is implied rather than stated: the tool is for fetching 'new alerts', and refresh=true is recommended only when you want a check run 'right now'. There is no when-not-to-use guidance and no alternative named for retrieving event changes or managing alert settings. The 'empty list means nothing new' note is useful but is interpretive rather than routing guidance.

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