web_dev_html_to_markdown

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

No annotations are provided, so the description must carry the burden. It only states 'Convert HTML code to Markdown format online' without disclosing any behavioral traits such as statelessness, rate limits, or output format. It lacks context about processing limitations or auth needs.

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 short (3 sentences) and front-loaded with the core purpose. However, the 'Menu ID: html_markdown' line adds little value and could be removed. The reference to describe_tool is helpful but slightly clutters the main message.

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?

Given the tool has 2 required parameters (one nested), no output schema, and no annotations, the description is severely incomplete. It does not mention return values, error handling, or any details about the options object, leaving a significant information gap for the agent.

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 0%, and the description does not explain the parameters ('html', 'options') or their purpose. It does not describe the nested options object with its three boolean properties, leaving the agent with no guidance on parameter values.

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 clearly states 'HTML to Markdown Converter' and specifies use cases like web content, emails, and documents. It uses a specific verb (Convert) and resource (HTML to Markdown), distinguishing it from siblings like web_dev_markdown_to_html.

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 does not provide explicit guidance on when to use this tool vs alternatives. It mentions using describe_tool for full guidance, but no direct comparison to siblings like web_dev_markdown_to_html or webdev_html_minifier.

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