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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds the balance scope and default ordering, but says nothing about pagination behavior (limit/offset exist), result size, or how filtered/empty results behave. With annotations doing the heavy lifting, this is adequate but thin.

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?

One front-loaded sentence with no padding; the scope and ordering are stated immediately. It is efficient, though arguably too terse given the parameter surface.

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?

Seven optional parameters, no output schema, and no annotations to fill behavioral gaps—yet the description covers none of the filtering, paging, or result-shape questions an agent must answer. For a paginated list tool with this much schema surface, it leaves too much undocumented.

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 only 57%, and the description mentions no parameters at all. It never explains what the free-text search matches, how the type array values map to the table's type names, or whether date filters are inclusive—areas where the schema only partially compensates.

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?

It names the resource concretely—every charge, payment and refund on the Pirate Ship balance—so an agent knows what object it returns. It does not distinguish this list from close siblings such as list_refunds, list_receipts or list_carrier_adjustments, nor state an explicit verb.

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 statement of when to use this versus alternatives, and no exclusions. Several sibling list_* tools cover overlapping data (refunds, receipts, adjustments), and the description gives no guidance on picking between them.

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