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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the tool strips navigation/footer when extractContent is set, but that duplicates the schema; it says nothing about network/rate-limit behavior from fetching a URL or what a failed fetch returns.

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?

A single sentence that front-loads the core action and packs the two input modes plus the optional extraction behavior without filler. Every clause carries information.

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 read-only converter with no output schema, the description should at least state the return shape (a Markdown string) and conflict/error behavior when url fetch fails or both inputs are given. It is adequate for calling the tool but leaves the result contract implicit.

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 100%, so all three parameters (url, html, extractContent) are already documented at the same level the description provides. The description's 'optional if html provided' restates the schema's mutual-optionality without adding format or precedence rules.

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 gives a specific verb (convert), resource (HTML/web page), and output (Markdown), plus both accepted input modes (URL or raw HTML string). It is clear on its own, but it never distinguishes itself from the sibling get_page_markdown, which an agent could easily confuse with this tool.

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 explicit when-to-use guidance, no mention of what to do when both url and html are supplied, and no differentiation from get_page_markdown or the other page-oriented siblings. Usage is only inferable from the phrase 'by URL or a raw HTML string'.

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