convert_url

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 discloses the output format (Markdown and metadata) which is helpful, but it does not mention that the tool fetches the webpage over the network, potential delays, or any failure modes. The description is adequate but lacks deeper behavioral context.

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 two sentences, with the primary action front-loaded. It avoids repetition and every phrase adds value: the verb, the resource, the output format, and the specific metadata returned. No unnecessary words.

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's moderate complexity and lack of output schema, the description covers the core behavior (conversion to Markdown) and return metadata. It does not explain tool selection among conversion-related siblings, which would improve completeness, but for a simple conversion tool it is mostly adequate.

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 covers all parameters with descriptions (100% coverage), including the URL format and boolean toggles for links and images. The description adds some context by mentioning metadata like 'title, word count, reading time' but does not clarify how 'includeLinks' or 'includeImages' affect the output. Baseline of 3 is appropriate since schema does the heavy lifting.

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 uses a specific verb 'Convert' with a clear resource ('a webpage URL') and outcome ('to clean Markdown'), and further specifies the return value ('Markdown content and metadata'). It distinguishes itself from sibling tools like 'semantic_search' by clearly stating its conversion purpose, though not explicitly comparing to other conversion tools, it is still specific enough.

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 states what the tool does but gives no guidance on when to use it versus alternatives. With siblings like 'bridge_convert_url', 'agent_convert', and 'agent_batch_convert', there is no mention of selection criteria, prerequisites, or scenarios where this tool is preferred. This is a clear gap.

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