html.to-markdown

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

Discloses that scripts/nav/ads are stripped and main content is extracted, preserving headings/links/lists. Lacks details on error handling or size limits beyond schema, but adequate for a simple conversion.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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?

Covers purpose, limitations (no URL fetch), and output format implicitly. Could mention return value explicitly, but given no output schema, it's sufficient.

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 covers the single parameter well (100%). Description adds little beyond restating 'Raw HTML (<=2MB)' and context of already having the HTML.

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?

Clearly states 'Convert raw HTML ... into clean reading markdown' with a specific verb and resource. Distinguishes from sibling url.clean by specifying 'no URL fetch'.

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?

Explicitly says 'no URL fetch' and directs to url.clean for live URLs. Also describes stripping of unwanted elements, guiding appropriate use.

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