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

With no annotations, the description carries the full burden. It discloses that JavaScript-rendered content may be incomplete, which is a behavioral limitation. It details the quality object and the two quality_check modes, noting that AI checks are off unless requested and that no source comparison is performed. This is rich behavioral context beyond what schema provides.

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 multi-paragraph but each sentence contributes useful information. It front-loads the core purpose and then details parameters and behaviors. It could be slightly more concise, but the length is justified given the complexity of quality_check. No fluff.

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 3 parameters and no annotations or output schema, this description is quite complete. It explains the return quality object, the parameter usage, and limitations. Minor gaps: it doesn't mention error handling for invalid URLs, authentication requirements (beyond public access), or response structure for success/failure. But overall, it covers the essentials for an agent to decide and call.

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?

Schema coverage is 0%, so the description must compensate. It explains the purpose of filename_hint and quality_check, adding meaning to those parameters. However, it doesn't detail the format or constraints of the 'url' parameter beyond 'publicly accessible', which is already in the description. Overall, it adds value but could be more detailed on URL validation or examples.

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 verb (fetch and convert), the resource (URL), and the output (Markdown). It distinguishes from siblings by indicating it handles URLs, whereas convert_base64 presumably handles base64-encoded input. The mention of supported document types adds specificity.

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?

Explicitly states it works on publicly accessible URLs, mentions the filename_hint for format detection, and clarifies the quality_check options. While it doesn't explicitly say when NOT to use it, it implies using other tools for non-URL inputs. The distinction between basic and AI quality checks is clear.

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