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

No annotations are provided, so the description carries the full burden. It clearly states the behavioral transformation: stripping HTML tags and decoding entities. It does not disclose edge-case behavior (e.g., handling of script/style content or malformed HTML), but for a simple conversion utility the core behavior is sufficiently transparent.

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, well-formed sentence that is front-loaded with the action and delivers the key information without any fluff. Every word contributes meaning.

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 simple, stateless conversion tool with one parameter and no output schema, the description is complete: it states the input and the transformation. It does not detail return value format, but that is implied by 'to plain text' and is unlikely to cause confusion.

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 has one parameter with a description ('HTML string to convert') and 100% coverage. The tool description adds no additional meaning beyond the schema; it simply restates the purpose. This matches the baseline for high schema coverage.

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 ('Strip') and resource ('HTML tags') plus the outcome ('decode entities to plain text'). It is unambiguous and distinct from sibling tools like markdown_to_html, which does the opposite conversion.

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 description gives no explicit guidance on when to use this tool or how it compares to alternatives. No exclusions or alternative tool names are mentioned, leaving the agent to infer the use case solely from the tool name and description.

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