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

The description goes well beyond the annotations by explaining the x402 payment requirement for metered buyers, the 402 status with accepts[], and the access-scope guarantee. It also implies a non-idempotent, state-changing operation consistent with readOnlyHint=false and idempotentHint=false. No contradiction with 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?

Three dense sentences deliver the core action, authentication requirement, payment caveat, and data-scope guarantee without wasted words. The most important operational detail ('Drain the queue') 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?

Given the lack of an output schema, the description adequately covers the main response concept ('Records are projected to the scope...'). It could add what happens on an empty queue or when the buyer key is invalid, but these are not essential for selecting and invoking the tool correctly.

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 75%, so the schema carries most parameter meaning. The description adds context for the payment parameter via the x402 requirement and states that the buyer_key is required, but it does not explain the mandate or credential parameters beyond their schema descriptions.

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 uses a specific verb ('Drain') and resource ('queue of pool records routed to you'), and the title adds 'buyers' to clarify the intended actor. This clearly distinguishes it from the sibling tools, none of which describe pulling routed records.

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 description makes the usage context clear: it is for buyers retrieving routed pool records and requires the buyer key. It does not explicitly name alternative tools or state when not to use it, but none of the siblings are close alternatives, so the guidance is adequate.

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