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

No annotations are provided, so the description carries full burden. It discloses only that HTML tags are stripped, but does not mention whether text content is preserved, whether entities are decoded, whether script/style content is removed, or what the output format looks like. This is minimal behavioral disclosure.

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 description is one sentence and directly states the operation. It is appropriately small, though the repeated 'Strip HTML: Strip HTML tags' adds slight redundancy with the title/name.

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 one-parameter text-processing tool, the description is simple, but with no output schema and no annotations, an agent lacks clarity on output behavior, edge cases (e.g., malformed HTML, script tags), and whether this differs from sibling strip tools. Minimal completeness for a straightforward utility, but clear gaps exist.

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 100%: the single parameter 'html' is described as 'Html to process'. The description's 'HTML tags from text' reinforces that the parameter is the HTML source. With only one simple parameter and full schema coverage, no additional parameter explanation is needed.

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 states a specific verb ('Strip') and resource ('HTML tags from text'), making the core purpose clear. It doesn't explicitly distinguish from similar siblings like x402-strip-tags or x402-html-text-extract, but the name and description together communicate the operation adequately.

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?

No guidance on when to use this tool versus alternatives. Siblings like x402-strip-tags, x402-html-text-extract, x402-html-to-markdown, or x402-remove-emoji could overlap, and the description does not clarify the intended use case or exclusions.

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