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

The description adds valuable behavioral context beyond annotations: buyer key authentication, the x402 payment requirement with status 402 and accepts[], and the security guarantee that records are projected only to the consumer's granted scope. I do not see a true contradiction with destructiveHint=false, since 'drain the queue' reflects retrieval/consumption of queued records rather than permanent data destruction.

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 with no filler. The core action is front-loaded, followed by authentication, payment behavior, and scope projection. Every sentence earns its place.

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?

The description covers authentication, payment, and scope, but with no output schema it does not describe the success response format or what happens to records after the queue is drained. For a tool with this level of behavioral nuance, that is a notable gap but not crippling.

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 already documents mandate, payment, and credential. The description adds useful context for buyer_key and the payment flow, but it does not meaningfully explain the optional parameters beyond what the schema 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 states a specific action and resource: drain the queue of pool records routed to the caller. It also clearly establishes the buyer context, distinguishing it from siblings like get_quotes or check_eligibility.

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 clearly explains when to use the tool: when you are a buyer with routed records, and it notes the buyer key requirement plus the payment condition for metered buyers. It does not explicitly mention alternatives or when not to use it, so it stops short of a 5.

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