webpage-to-markdown

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'convert' implies a transformation operation, the description doesn't reveal any behavioral traits: it doesn't mention whether this requires internet access, what happens with complex webpages (JavaScript, authentication), error handling, or output format details beyond 'markdown'.

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 extremely concise at just four words, with zero wasted language. It's front-loaded with the core purpose and uses clear, direct phrasing that immediately 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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what the markdown output contains (full content, metadata, links), how it handles webpage elements (tables, images), or any limitations (size, complexity). Given the context of conversion tools with various source types, more guidance is needed.

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 100% description coverage, with the single 'url' parameter clearly documented. The description doesn't add any parameter semantics beyond what the schema provides (it doesn't elaborate on URL format requirements, encoding, or validation), so it meets the baseline score when schema coverage is high.

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 the tool's purpose with a specific verb ('convert') and resource ('webpage'), making it immediately understandable. However, it doesn't distinguish this tool from its siblings (like 'pdf-to-markdown' or 'youtube-to-markdown'), which all follow the same pattern of converting different source types to markdown.

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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools that convert different source types to markdown (audio, PDF, YouTube, etc.), there's no indication that this is specifically for webpages versus other document types, nor any mention of prerequisites or limitations.

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