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

Beyond the minimal annotations, the description discloses queue-draining/consumptive behavior, the x402 payment requirement with status 402 and accepts[], and the scope-projection guarantee ("never wider"). It also states the auth prerequisite ("Requires your buyer key"), all of which are behavioral traits not visible from annotations alone.

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?

The description is three sentences with no filler: the core action is front-loaded, followed by the requirement, the payment caveat, and the security scope note. Every sentence contributes distinct information.

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?

It covers what the tool does, auth requirements, payment behavior, and scope projection, which is substantial for a tool without an output schema. The return payload shape is not explicitly described, but "drain the queue of pool records" strongly implies the records are returned. This leaves only a small gap.

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?

The schema already documents 75% of the parameters (mandate, payment, credential), and the description only adds that buyer_key is required. The payment-flow explanation gives context but does not map parameters to payload fields or add meaningful semantics beyond what the schema descriptions provide. This matches the baseline for high schema coverage.

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 uses a specific verb "drain" acting on "the queue of pool records routed to you," making both the operation and resource unmistakable. The title "Pull routed records (buyers)" reinforces this and sets it apart from sibling tools like agency_status and 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?

The description gives clear context: it is for buyers pulling records routed to them, and it states the buyer_key prerequisite and the condition for metered buyers receiving a payment requirement. It does not explicitly name alternatives or say when not to use the tool, 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.