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

The description reveals that mark_read:true flags events as read, which modifies state, contradicting the readOnlyHint:true annotation. This is a serious inconsistency because the annotation claims read-only behavior while the tool can mutate read status. Therefore, the description contradicts the annotations.

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 description is four sentences, each serving a distinct purpose: core function, payload composition, filtering options, and behavioral nuance plus alternative access. It is tightly written with no redundancy, front-loading the action verb and resource.

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 compensates by detailing what each alert contains (source, citation_uri, raw payload), covering filtering and mark_read behavior, and noting an alternative HTTP endpoint. It fully equips an agent to select and use the tool correctly, including polling suitability.

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 100% means the schema already documents all parameters. The description adds meaningful value by explaining the consequence of mark_read (only newer events on next call) and giving a concrete type filter example. This goes beyond the baseline of 3, warranting a 4.

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 clearly states the tool pulls recent alerts from the subscription feed and describes the payload fields, making the purpose specific and unambiguous. However, it does not explicitly differentiate from sibling tools like recent_changes, so it falls short of a 5.

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?

The description gives clear context: it mentions polling works fine and points to an HTTP endpoint for scripts, which provides guidance on when to use the tool versus external access. It also explains the mark_read effect for subsequent calls, implying a polling workflow. No direct comparison with sibling tools, but the context is sufficient.

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