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

With no annotations, the description carries the full burden, and it does disclose real algorithm behavior: line width defaulting to 40, breaking at whitespace, and trimming the result. It says nothing about error handling, what happens on words longer than the width, or the payment/auth requirement implied by the free-trial note.

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?

One front-loaded sentence that states the operation and its defaults before anything else, with no filler. The appended free-trial promo is extraneous to the tool's function and slightly dilutes an otherwise tight 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 and no annotations mean the description is the only source of truth, yet it omits the return shape and the text-vs-input ambiguity. For a 3-parameter tool with 0% schema documentation, this leaves an agent guessing at call construction.

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 coverage is 0% across three parameters. The description partially compensates by documenting 'width' and its default of 40, but it never explains why both 'text' and 'input' exist or which one takes precedence, leaving the primary input ambiguous.

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 ('Wraps text into lines of the given width') and adds concrete mechanics (whitespace breaking, trimming, default 40). However, it never differentiates itself from the near-identical siblings x402-text-wrap and x402-word-wrap, so an agent cannot tell which one to pick from the description alone.

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 statement of when to use this tool versus x402-text-wrap/x402-word-wrap, nor any prerequisite or exclusion. The only contextual sentence is a pricing promo ('5 free trial calls per signed wallet'), which is commercial info rather than usage guidance.

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