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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing that the default view is scoped to the published version while the by-id view exposes all versions. It does not address pagination, auth requirements, or how archived rules interact with the result set.

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?

Two tight sentences: the first establishes what event rules are, the second delivers the mode semantics. Nothing is repeated from the schema and 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?

For a read-only two-mode listing tool with no output schema, the description conveys the shape of results reasonably well (rules plus versions). However, it leaves include_archived undefined and gives no hint of result limits or ordering, so an agent could call it correctly but not fully predict the response.

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 only 33% (only site_id is described), so the description must compensate. It does explain event_rule_id's effect in mode terms, but says nothing about include_archived, which is undocumented in both schema and description — a real gap for a filtering flag.

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 states the resource (event rules) and what they are ('turn clicks, form submits and page views into named custom events without code'), then says precisely what the call returns in each mode. It is specific enough to distinguish from siblings like list_links or list_visits, though it never names those siblings explicitly.

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 gives a clear conditional: omit event_rule_id to list rules with their published version; supply it to expand every version and its rules. That is genuine when-to-use guidance for the one ambiguous parameter. It stops short of exclusions or pointing at any alternative tool.

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