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

Annotations only declare the mutation/idempotency profile; the description adds genuinely new behavior: it is asynchronous, costs $0.05 per file billed in USDC on Solana, and caps at 100 files. It omits what happens on partial batch failure and how completion is signaled, which are meaningful gaps for an async job.

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?

A single dense passage with the action first, then price/limits, then payment protocol, then the HTTP equivalent. Every clause carries operational information and nothing is padded.

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?

With no output schema and an asynchronous operation, the description should explain how results are retrieved (poll a job id, receive a callback, etc.), but it does not. Combined with the empty input schema versus the stated 100-file capability, an agent knows the payment ritual but not how to submit files or collect the converted PDFs.

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?

Zero-parameter schema, so the baseline is 4. However, the description mentions 'up to 100 files per batch' while the input schema declares no properties at all, leaving it unclear how the Publisher files are actually supplied; a note on the input mechanism would have earned a 5.

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?

States a specific verb and resource ('Batch-convert Publisher files to PDF') with the async qualifier front and center, so it is clearly distinguishable from the single-file sibling pubconvert_convert. It does not explicitly name that sibling or contrast with it, which keeps it from a 5.

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?

Gives concrete procedural guidance on the x402 flow (call without payment to receive the PaymentRequired challenge, then retry with payment at _meta["x402/payment"]) and states the batch ceiling of 100 files. It stops short of saying when to prefer this over pubconvert_convert or pubconvert_verify.

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