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

Beyond the annotation readOnlyHint=false, the description discloses that the operation drains a queue, requires a buyer key, may impose an x402 payment requirement with status 402 and accepts[], and enforces consumer-granted scope. This adds meaningful behavioral context, though it does not specify whether drained records are permanently consumed or how repeated calls behave.

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, with the core action front-loaded and every sentence adding operational value: what it does, prerequisites, payment behavior, and scope constraint. There is no filler.

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, yet the description never mentions the response shape, return format, or behavior on an empty queue. It covers authentication, payment, and scope well, but leaves an agent without enough information about what the tool actually returns beyond the mention of records.

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% and already explains mandate, payment, and credential well. The description adds important semantics for buyer_key ('Requires your buyer key') and explains why payment-related fields exist for metered buyers. This goes beyond the schema without duplicating it.

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 ('Drain the queue') on a specific resource ('pool records routed to you'). It clearly distinguishes the tool as a buyer-side pull operation, which is unique among the listed siblings and leaves no ambiguity about what it does.

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 gives clear context: use this to consume records routed to you as a buyer, and it notes the buyer key requirement. However, it does not explicitly state when to avoid this tool or name alternative tools for other scenarios, so it stops short of full routing guidance.

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