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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no ordering guarantee, no default limit, no pagination or retention window, which are the behaviors that actually matter for an event feed.

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?

A single front-loaded sentence with no filler, and the event-type enumeration is compact. It earns its place, though the informal phrasing ('scores that moved, rules that were fixed') costs some precision.

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?

For a zero-required-param read tool this is nearly adequate, but with no output schema the description should say something about the shape of an event (what fields, whether it is ordered newest-first, default count). The event-type list hints at content but leaves the return contract opaque.

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 100% (site, limit both documented in-schema), so the baseline of 3 applies. The description contributes no additional parameter meaning, such as what 'site' accepts or what the default limit is.

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 conveys that this is a recency-ordered event feed and enumerates event kinds (reads requested/finished/failed, score changes, rule fixes), which gives real content flavor. But it never states a verb ('list', 'returns') or the resource name directly — the reader has to infer 'events' from the title — and it distinguishes nothing from near-siblings like mttr_changes, mttr_progress_link, or mttr_queue.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no mention of how this differs from the many other listing tools in the sibling set. The agent must guess whether this is a dashboard feed, an audit log, or a job history.

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