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

Beyond the annotations, the description discloses several concrete behaviors: the queue-draining effect, the x402 payment requirement with status 402 and accepts[], and the security guarantee that records are projected only to the granted scope. This adds meaningful context about side effects, authentication, and authorization that the boolean annotations do not convey.

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 sentences deliver purpose, prerequisites, payment behavior, and security scope with no filler. Each sentence earns its place, and the most important action is front-loaded.

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 core action, required key, payment edge case, and data scoping. Since there is no output schema, one might want a bit more about the exact return shape or what happens after the queue is drained, but "drain the queue" strongly implies the outcome. Overall it is sufficiently complete for a capable agent.

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 schema already documents mandate, payment, and credential. The description fills the gap for buyer_key by stating it is required, and it explains the role of payment in resolving the 402 status. This adds meaningful semantic context beyond the bare schema fields.

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 a specific verb and resource: "Drain the queue of pool records routed to you." This clearly distinguishes the tool from sibling tools like agency_status or get_quotes, which serve different functions. The title reinforces the buyer-facing scope.

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 states the prerequisite clearly: "Requires your buyer key." It also gives conditional usage context by explaining that metered buyers need to supply x402 payment until the 402 requirement is satisfied. It does not explicitly name alternatives or when not to use the tool, but the context is clear.

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