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

Annotations only cover safety/idempotency, so the description adds substantial behavioral context: a 64 KB size cap, 'no external call', decode-to-hex behavior for non-UTF-8 bytes, and the crucial workflow detail that bad input is refused before any charge.

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?

Front-loaded with the use condition, and every sentence carries weight (limits, pricing, rejection-before-charge). It is a dense single paragraph, slightly run-on, but no filler.

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, the description compensates by explaining the x402 payment workflow, the returned request shape, the price, and that a response schema plus example are included. An agent has enough to invoke and follow through 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?

Schema description coverage is 100%, so the baseline is 3. The description clarifies the url_safe variant (no padding) and the hex decode fallback, but mostly restates what the schema already documents.

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 specific verbs and resources: encode UTF-8 text to base64 (standard or url_safe) or decode base64 back to text, with hex fallback for non-UTF-8 bytes. An agent can distinguish this from siblings like util_hash or util_jwt_decode without opening either schema.

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?

'Use when you need base64 in or out' gives a clear triggering condition, and it outlines the encode/decode choice. It doesn't explicitly name sibling alternatives, but the trigger context is unambiguous.

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