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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description usefully reinforces that this is read-only and clarifies the data universe (already-occurred payments/refunds/credits). It adds a concrete pagination behavior (feed next_offset back as offset), though it says nothing about rate limits or reply size beyond include_applied_to.

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?

Front-loaded verb and scope, then the field inventory, then paging and the underlying endpoint. The long field run-on is dense but each item is load-bearing, and the trailing 'GET /transaction' is a minor implementation detail.

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 partially compensates by disclosing paging via next_offset and the include_applied_to reply-size tradeoff. It does not describe the returned transaction record shape, but for a list tool with a fully documented filter schema this is a minor gap.

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 earns above that by enumerating the valid filter field names — which the schema itself defers to ('the list tool's description names the valid ones'). Without this list an agent could not construct valid filters; the description does not, however, explain operator/value pairings beyond what the schema shows.

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 transactions') and sharpens the scope with 'payments, refunds and credits that already happened; this tool only reads them.' It does not explicitly contrast itself with chargeover_get_transaction or the other list_* siblings, so a 4 rather than 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?

There is no explicit statement of when to choose this tool over chargeover_get_transaction or the other list_* tools, and no exclusions or prerequisites. The paging note ('pass next_offset as offset') is an operational hint, not tool-selection guidance.

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