list_payments

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

With no annotations, the description carries the full disclosure burden; 'List' conveys a read-only operation and 'payment history' indicates the returned domain. It does not, however, disclose pagination, ordering, result shape, or any account-specific behavior beyond what the parameter schema covers.

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?

A single short sentence states the action, resource, and scope with no filler or duplicated schema information. The most important operand ('payment history') is front-loaded.

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 one-parameter, read-only list tool this is close to sufficient, but there is no output schema and no description of the returned fields, ordering, or pagination. The missing usage guidance and absent behavioral notes leave an agent with less context than it could reasonably have.

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%, so the schema already documents the single optional 'account' parameter and its auto-detection behavior. The description adds only that the history belongs to the AdSense account, which is already implied by the tool scope, not new parameter semantics.

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?

Description states an explicit verb+resource ('List payment history') and scopes it to the user's AdSense account, which differentiates it from sibling list tools focused on accounts, ad clients, ad units, and sites. The name is not merely restated.

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?

The phrasing implies this is the tool to use when payment history is needed, and the scope 'for your AdSense account' provides some context. However, no explicit when-to-use or when-not-to-use guidance is given, and none of the alternatives such as generate_report or list_alerts are referenced.

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