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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds only that entries are credits and debits; it says nothing about pagination behavior, ordering, or result volume, all of which matter for a ledger listing.

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 short fragments, front-loaded with what is returned before the endpoint reference. Nothing wasteful, though the second fragment is arguably redundant with the tool name and annotations.

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?

No output schema exists, so the description carries the burden of describing return values. It hints at credits/debits but does not describe entry fields, ordering, or pagination across pages, leaving the agent with only a thin picture of what comes back.

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% and both parameters are documented there, including pagination semantics ('page number, from 1'; 'pass the previous reply's next_page'). The description only restates the token via the path template, adding no meaning beyond the schema.

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?

Names the specific resource (ledger entries of one subscription) and clarifies what a ledger entry is (credits and debits), and the endpoint template pins down the scope. It cannot be confused with pinpayments_get_subscription, which returns the subscription itself rather than its ledger.

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?

No guidance on when to use this instead of pinpayments_get_subscription or the other list/get siblings, and no prerequisites or exclusions. The agent must infer usage from the endpoint line alone.

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