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

With no annotations provided, the description carries the full burden of disclosing behavior. It states that dangerous tags and attributes are removed, but does not explain what 'dangerous' means, how the 'level' parameter affects behavior, whether content is preserved outside those tags, or what the output looks like. Significant behavioral details are missing.

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 a single concise sentence that is front-loaded with the main action. Every word earns its place; there is no fluff or redundancy.

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?

The tool has three parameters with an enum and no output schema or annotations. The description provides a high-level purpose but does not explain sanitization levels, empty-element removal, or return format. A bit more context would be useful, but the schema fills in parameter details, making it minimally adequate.

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?

The schema fully documents all three parameters (html, level, removeEmpty) with descriptions, so the baseline is 3. The tool description adds no additional meaning beyond the schema—it only mentions 'dangerous tags and attributes,' which relates to the 'html' parameter but does not enrich understanding of 'level' or 'removeEmpty'.

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 uses a specific verb ('Sanitize') and resource ('HTML') and states the exact action ('removing dangerous tags and attributes'). This clearly distinguishes the tool from siblings, none of which are sanitizers.

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?

The purpose is self-evident, implying usage for cleaning HTML, but there is no explicit guidance on when to use vs. alternatives, prerequisites, or exclusions. It does not name any alternative or say 'use when...'.

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