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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that results include payments and refunds; it does not disclose ordering, pagination behavior, or what is omitted, so it adds modest value beyond annotations.

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?

The description is a single sentence with no filler, and the resource scope is front-loaded. It is concise, though it could be structured as a complete verb phrase to make the operation clearer.

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?

For a five-parameter read-only list tool with no output schema, the description should clarify return content, pagination, or ordering at least minimally. It only hints at payments and refunds and leaves the agent to infer how the list is organized and how to traverse it.

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%, and all five optional parameters are documented in the schema, including limit, cursor, search, start_date, and end_date. The description adds no additional filter syntax or parameter semantics beyond what the schema already provides.

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?

The description identifies the resource as charged bookings with payments and refunds and ties it to the Charges page, but it never uses an explicit list/retrieve verb and does not distinguish this tool from siblings such as list_bookings, list_invoices, or refund_charge.

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 no guidance on when to use this tool rather than list_bookings, list_invoices, or refund_charge, and it states no prerequisites, exclusions, or filtering intent beyond the schema itself.

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