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

The description adds meaningful behavioral context beyond the annotations: the buyer key requirement, the metered payment mechanism with status 402 and accepts[], and the privacy-oriented scope projection ('never wider'). The annotations only carry false hints, so the description carries the burden and fulfills it well. No contradiction with annotations was found.

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 compact sentences deliver the core action, prerequisites, payment behavior, and scope constraints. The most important information is front-loaded, and every sentence contributes distinct value. No filler or repetitive wording.

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 tool with no output schema, the description covers the essential invocation context: action, prerequisite, conditional payment, and data projection scope. It does not describe the shape of returned records or what 'draining' means for queue state in detail, but the description is sufficient for an agent to understand the operation and its conditions. Slight gap around return semantics keeps it from a 5.

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 description adds value by clarifying that buyer_key is the caller's required key and explaining the role of the payment parameter in the x402 flow. This goes beyond the raw schema, which leaves buyer_key undescribed. The mandate and credential parameters are not elaborated further, but the existing schema descriptions cover them.

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 of pool records routed to you'—with a clear resource and scope. The title 'Pull routed records (buyers)' reinforces the intended audience. It does not explicitly distinguish itself from sibling tools, but the verb and resource are specific enough that an agent can identify 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 provides clear context for when to use the tool: to drain queued records routed to the caller. It also states a prerequisite ('Requires your buyer key') and a conditional requirement for metered buyers ('receive an x402 payment requirement until a payment is supplied'). It does not explicitly name alternatives or exclusions, but the conditions are clear.

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