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

The description adds meaningful behavioral detail beyond the minimal annotations: it discloses the buyer-key requirement, the x402 payment requirement for metered buyers, the status 402/accepts[] condition, and the projection scope limitation. It could mention what 'drain' does to the queue in more detail, but the disclosed behavior is substantial.

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 concise sentences, each adding distinct value: purpose, prerequisite, payment behavior, and scope constraint. There is no redundant or filler text, and the most important information 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?

For a tool with no output schema and only basic annotations, the description covers the main operational context: what it does, who it is for, the payment edge case, and the security scope. It does not describe return format or empty-queue behavior, but these are secondary given the clarity of the rest.

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 already documents mandate, payment, and credential, providing 75% coverage. The description reinforces the buyer_key requirement and explains the payment-related parameters in context, but it does not add significant new meaning beyond the schema. With coverage near 75%, a mid-range score is appropriate.

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 audience (buyers). It is immediately distinguishable from siblings like agency_status or get_quotes, which serve different purposes.

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: use this when you have a queue of pool records routed to you, and you need your buyer key. It does not explicitly name alternatives or when-not-to-use conditions, but no sibling tool performs a similar operation, so the context is sufficient.

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