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

Annotations already declare readOnlyHint=true, but the description adds real value beyond that: the log is immutable, pagination is cursor-based via JSON:API links, and payloads 'may reference PII'. It stops short of describing auth/permission requirements or rate limits, but the sensitivity warning and pagination mechanics are substantive.

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 dense sentences with no filler; the purpose leads, then pagination, then return shape and sensitivity, then the REST endpoint. Tight, though the trailing 'GET /events' line is the least load-bearing element.

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?

There is no output schema, so the description compensates by describing the JSON:API { data, links } return shape and the PII caveat. With all three optional params covered by the schema, an agent has everything needed to call and paginate this read-only endpoint correctly.

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%, so the baseline would be 3, but the description adds the wiring that the schema lacks: page_after corresponds to links.next and page_before to links.prev, telling the agent how to obtain and use those cursors. That is meaningfully more than the parameter docs alone.

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 and resource ('List audit-trail events') and immediately defines the resource in operational terms ('an immutable log of actions ... inquiry/account/case state changes'), which unambiguously separates it from the sibling persona_get_event (single record) and from the other persona_list_* tools.

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 operational guidance on how to page (follow links.next/links.prev) but never states when to choose this over persona_get_event or another listing tool, nor any prerequisites. Usage is implied by the description rather than spelled out.

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