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

Even with annotations declaring readOnly=false, destructive=false, and idempotent=false, the description adds meaningful behavior: the x402 payment requirement with status 402 and accepts[] until paid, plus the scope-projection guarantee ('never wider') and the queue-draining, non-idempotent nature. It does not contradict the annotations and adds context beyond them.

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 short sentences pack behavior, auth requirement, payment condition, and data-scope guarantee with no filler. The most important 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?

For a pull operation with no output schema, the description adequately covers what the tool does, who may call it, the metered-payment 402 behavior, and the scope constraint. It would be stronger with an explicit statement about the response shape or records list, but the first sentence makes that reasonably inferable.

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 the description usefully explains that buyer_key is required and that payment is needed for metered buyers (status 402/accepts[]). However, it does not clarify when to supply mandate versus credential or how they relate to the x402 payment, leaving the three optional payment-related parameters ambiguous.

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,' naming a specific action and object, and the title 'Pull routed records (buyers)' reinforces it. This clearly separates it from sibling tools like get_quotes or market_data, which do not describe consuming a buyer-specific routed queue.

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 gives a clear use context: use this when records are routed to you as a buyer and you need to drain the queue. It also states prerequisites ('Requires your buyer key') and the conditional payment path for metered buyers, though it does not name exclusions or alternative tools.

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