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

With no annotations, the description carries the full behavioral burden. It does disclose the exact transformation set (four character classes converted to HTML entities), which is the key behavior for an escaper, but says nothing about idempotency, whether already-escaped entities are double-escaped, or return format.

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?

The purpose and the character list are front-loaded in a single efficient sentence. The trailing '🆓 5 free trial calls per signed wallet' marketing fragment is tolerable but does not help tool selection.

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 two-parameter, zero-annotation, no-output-schema tool, the description should resolve the text-vs-input ambiguity and any output expectations. It instead leaves the primary invocation question open, so it is not complete enough to call reliably.

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 the schema exposes two undocumented, ambiguous fields ('text' and 'input') with no indication of which is used or how they interact. The description mentions 'in text' but leaves 'input' entirely unexplained, so the agent cannot tell whether both are needed or one overrides the other.

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+resource ('Escape HTML') and enumerates exactly which characters are transformed (ampersands, angle brackets, double quotes, apostrophes), which is more precise than a bare title restatement. It does not differentiate from close siblings like x402-html-entity, x402-escape-special-chars, or x402-strip-html, so the agent must infer the boundary.

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 exclusion of alternatives, and no mention of the obvious reverse operation (unescape/entity-decode) or of the sibling escape utilities. The agent gets a purpose but no routing signal.

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