web_to_markdown

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

Discloses that scripts, styles, footer, navigation are removed, but no annotations exist. Lacks details on rate limits, authentication, error handling, or JavaScript execution. Adequate but not exhaustive.

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?

One sentence, front-loaded, no wasted words. Every part is essential and clearly communicates the tool's function.

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?

Simple tool with one parameter and no output schema. Description covers main behavior and output format. Could mention limitations like dynamic content handling, but remains fairly complete for its simplicity.

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?

Single parameter 'url' with schema description 'The URL of the webpage to scrape and convert.' Schema coverage is 100%, so baseline 3. Description adds no extra semantics beyond the schema.

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 verb (fetch, clean, convert), resource (web page), and output (Markdown). Differentiates from sibling tools like web_extract_links and web_extract_metadata by specifying conversion and clutter removal.

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?

Implied usage for converting web content to Markdown, but no explicit when-to-use or alternatives. With 40+ sibling tools, guidance on when to prefer this over others (e.g., web_extract_metadata) is missing.

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