web_dev_markdown_to_html

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

No annotations exist, so the description must disclose behavioral aspects. It mentions a real-time preview but omits critical details like return format, error handling, or safety profile (e.g., whether the tool mutates state). This is insufficient for an agent to predict side effects.

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 but includes filler like 'Menu ID: markdown_html' and a reference to another tool. It could be streamlined to focus on essential details. The structure is acceptable but not optimal.

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 complexity (nested options, no output schema) and absence of parameter descriptions, the description fails to equip the agent with enough information to invoke the tool correctly. Critical details about options and output are missing.

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 input schema has two required parameters (markdown string, options object with three booleans) with 0% schema description coverage. The description provides no explanation of what these parameters mean or how to use them, leaving the agent completely in the dark.

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 'Convert Markdown text to HTML online' with specific features (headers, lists, links, etc.), and the tool name contrasts with sibling web_dev_html_to_markdown, making intention unambiguous.

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?

While the description conveys the core function, it lacks explicit guidance on when to use this tool versus alternatives like web_dev_html_to_markdown. The mention of 'Use describe_tool...' suggests more info elsewhere but does not directly provide usage boundaries.

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