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

The description discloses significant behavioral details beyond the all-false annotations: the queue-draining effect, the x402 payment gate with status 402 and accepts[], and the scope-narrowing guarantee. This gives an agent a realistic model of what will happen and what constraints apply.

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 fluff: it leads with the core action, states the prerequisite, then explains conditional payment and data-scope behavior. Every sentence earns its place.

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 the main invocation contract: who can call it, what queue it affects, how metered payment works, and how scoping is constrained. It does not describe the success response shape or empty-queue behavior, but with no output schema and a clear action, it is still enough for an agent to invoke the tool correctly.

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 input schema covers three of four parameters, and the description adds contextual meaning by tying buyer_key to the required buyer identity and payment to the metered-buyer payment flow. The mandate and credential parameters are already explained in the schema, so the description does not need to repeat their syntax.

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 clear action and resource: 'Drain the queue of pool records routed to you.' It also establishes the buyer-specific context, which separates it from siblings like get_quotes or market_data. The title reinforces the meaning, so an agent can tell what this tool does at a glance.

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 should be used when a buyer wants to pull routed pool records, and it explicitly states the prerequisite of a buyer key. It also explains the payment requirement for metered buyers. However, it does not explicitly state when not to use it or name alternative tools.

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