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

With no annotations, the description carries the full disclosure burden. It only adds payment context (five free trial calls per signed wallet), disclosing nothing about what the tool computes, whether conversion is deterministic, what auth/signing is required beyond the trial, or what is returned.

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?

It is short and front-loaded, but the second sentence is pricing boilerplate rather than tool semantics. Brevity here reflects under-specification rather than disciplined editing.

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?

A three-parameter conversion tool with no annotations, no output schema, and 0% schema coverage leaves the agent entirely unequipped: no unit vocabulary, no indication of required inputs, no return-shape expectations. The description does nothing to fill that gap.

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% across three parameters (to, from, value). The description never explains that these are unit identifiers versus the numeric amount, gives no accepted unit names or formats, and adds no meaning whatsoever beyond the bare property names.

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?

"Pressure Unit: Pressure of unit" restates the tool name without stating an action verb or resource meaningfully. It never says this converts pressure values between units, nor which units are supported, so an agent cannot distinguish it from siblings like x402-pressure, x402-bar-to-psi, or x402-atm-to-pascal.

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 at all. The dozens of overlapping pressure and unit-conversion siblings (x402-pressure, x402-psi-to-bar, x402-units-convert, x402-speed-convert) make a routing hint essential, and none is given.

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