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

Annotations already establish readOnlyHint=true, so the safety profile is covered; the description adds genuinely non-obvious context beyond that — the return envelope is JSON:API {data:[...], links}, cursors come from links.next/links.prev, and returned objects may contain PII. It does not state rate limits or auth requirements, keeping it short of a 5.

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?

Three dense, front-loaded sentences: purpose, filtering/pagination, then return shape and sensitivity. Every clause carries information, though the trailing REST endpoint notation is somewhat redundant given the tool name and adds slight clutter.

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 usefully discloses the return envelope, cursor mechanism, and PII exposure, and all five parameters are documented. It stops short of describing error behavior or empty-result semantics, but nothing essential for a correct call is missing.

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 100%, so the baseline is 3, but the description adds real semantic value by mapping page_after to links.next and page_before to links.prev, telling the agent how to obtain the cursor values rather than just what they mean. It does not elaborate on page_size bounds or filter value formats.

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 (List) plus resource (transactions) and even defines what a transaction record is — 'records submitted for transaction fraud/monitoring analysis'. It also grounds the tool in the Persona REST API (GET /transactions), which clearly separates it from the sibling persona_get_transaction.

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?

Explains the two optional filter axes (reference_id, transaction_type_id) and how pagination is meant to be driven from JSON:API links. It gives clear operating context but never states when to prefer this over persona_get_transaction or what to do when a filter returns nothing, so no explicit exclusions.

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