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

Beyond the annotations (readOnly=false, destructive=false), it discloses that the operation drains a queue, that metered buyers face an x402 payment requirement with accepts[] until payment, and that records are scope-projected to the consumer's grant. These are substantive behavioral details not present in the schema or 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 tight sentences: action, prerequisite/payment behavior, and scope safety. No filler, and the core action is front-loaded in the first sentence.

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 purpose, auth prerequisite, payment gating, and scope projection, but there is no output schema and the description does not explain what a successful call returns or what happens when the queue is empty. For a drain operation, return/empty-queue behavior would be useful.

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 coverage is 75%, and the schema already describes mandate, payment, and credential. The description adds meaning to buyer_key ('your buyer key') and explains the payment-related flow ('Metered buyers receive an x402 payment requirement...'), which helps an agent know when payment, mandate, and credential are relevant.

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 opens with 'Drain the queue of pool records routed to you,' a specific verb plus resource that clearly identifies this as a buyer-facing pull operation for routed records. The title 'Pull routed records (buyers)' reinforces the audience, and this is distinct from sibling tools like get_quotes or market_data.

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 provides clear context: use when there are pool records routed to the caller, and mentions the prerequisite 'Requires your buyer key' plus a payment condition for metered buyers. It does not explicitly enumerate alternatives or when-not-to-use cases, but the queue-routing context makes the usage situation clear.

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