paywall_list_settlements

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Behavior: read-only' is a restatement with no added value. The one genuinely new piece of context is the auth requirement ('needs PAYWALL_API_KEY'), which annotations cannot express. Return shape and pagination behavior are left undisclosed.

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?

Short and front-loaded: the resource and usage condition come first, the sibling exclusion second. It loses a point for restating the resource phrase twice ('your real on-chain USDC settlements (earnings)') and for the redundant 'Behavior: read-only' line already covered by 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?

There is no output schema, so the description is the only place to learn what a settlement record contains or how pagination behaves beyond the limit cap — and it says nothing about either. For a simple read-only listing tool with full annotation and schema coverage, the gap is real but modest.

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 the single 'limit' parameter is already documented in-schema with its default and maximum ('Default 50, max 200'). The description adds no meaning about the parameter, so the baseline of 3 applies.

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 precisely ('real on-chain USDC settlements (earnings)') and the bracketed '[x402 Paywall]' tag places it in the right tool family, distinguishing it from paywall_list_routes by name. The action verb is only implied by the tool name, not stated in the description, so it falls just short of the clearest tier.

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?

Explicitly states the selection condition ('Use when you want your real on-chain USDC settlements') and an exclusion with the named alternative ('Not for route configuration (use paywall_list_routes)'). This is exactly the when/when-not/alternative structure that removes inference.

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