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

With no annotations, the description carries the full behavioral burden. It usefully discloses the output convention (K/M/B/T suffixes, two decimals), which is real behavioral context, but says nothing about auth/payment requirements beyond the trial line, edge cases, or error behavior.

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 compact sentence with the transformation front-loaded; no filler. The emoji trial note is slightly distracting but does not bloat the definition.

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?

No output schema, no annotations, and 0% parameter documentation mean the description must do more than it does. The ambiguous duplicate parameters are left entirely unresolved, which is a material gap for a tool with no other documentation.

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% and there are two parameters (value, number) that appear to serve the same purpose. The description says only 'a number' and never explains which parameter to use or how the two relate, leaving a genuine ambiguity the agent must guess at.

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 transformation (abbreviates a number with K, M, B, or T suffixes and two decimals), so an agent can tell it is a numeric formatting tool. It does not differentiate itself from near-siblings like x402-format-compact or x402-data-size-humanize, which limits it to a 4.

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 prerequisites, and no mention of alternatives among the many formatting siblings. The only contextual note is a pricing line ('5 free trial calls per signed wallet'), which is payment metadata, not usage guidance.

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