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

With no annotations, the description carries the full burden. It does disclose the default indent (2) and a commercial constraint ('5 free trial calls per signed wallet'), which is genuine behavioral context beyond the schema. It says nothing, though, about what happens with malformed JSON, error responses, or whether output is returned as a string.

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 front-loaded sentence conveys the core behavior, with the pricing note appended. Nothing is padded, though the emoji/price tag is slightly noisy relative to the functional content.

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 trivial two-parameter transform with no output schema and no annotations, the description covers the essentials of what goes in and what comes out. It leaves error handling, output type, and sibling differentiation unaddressed, so it is adequate but not complete.

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 0%, so the description must compensate. It does explain 'indent' as a number of spaces with a default of 2 and implies 'value' is the JSON input, covering both parameters at a basic level. It does not address the schema's odd string typing for 'indent' or any input format constraints.

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 names a specific verb and resource ('Returns JSON from value pretty-printed') and states the formatting behavior, so an agent can tell this is a pretty-printer rather than a minifier or validator. However, it never distinguishes itself from close siblings such as x402-json-format, x402-json-toolkit, or x402-xml-pretty, leaving overlap ambiguous.

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?

There is no when-to-use guidance, no statement of when to prefer this over x402-json-format or x402-json-minify, and no preconditions. Usage is only inferable from the tool name and the word 'pretty-printed'.

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