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. It states the action ('convert') but does not disclose behavioral traits such as rate limits, authentication needs, error handling (e.g., for invalid URLs), or output specifics (e.g., formatting quality). This leaves significant gaps for a tool that likely involves web requests and content parsing.

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 a single, efficient sentence with zero waste. It is front-loaded with the core action and resource, making it easy to parse. Every word earns its place by conveying essential information without redundancy.

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 of web conversion (involving network calls, HTML parsing, and markdown generation), the description is incomplete. No annotations exist, and there is no output schema to clarify return values or errors. The description lacks details on limitations (e.g., JavaScript-rendered pages), making it inadequate for informed tool selection.

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 'url' parameter fully documented. The description adds no additional meaning beyond what the schema provides (e.g., URL format constraints or examples). With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 'Convert a webpage to markdown' clearly states the verb ('convert') and resource ('webpage'), specifying the output format ('markdown'). It distinguishes from siblings like 'audio-to-markdown' or 'pdf-to-markdown' by specifying the input source ('webpage'), but does not explicitly differentiate beyond the input type.

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. It does not mention prerequisites (e.g., URL accessibility), exclusions (e.g., dynamic vs. static pages), or comparisons to siblings like 'bing-search-to-markdown' for search results. Usage is implied by the tool name alone.

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