URL and PDF to Markdown

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

No annotations are supplied, so the description carries the full behavioral burden and does almost none of it. It never explains what happens on failed fetches, whether JavaScript-rendered pages are supported, how batch URLs are processed, whether output is one document or many, or how long a run may take. Only the adjective 'public' gestures at a real limitation.

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?

A single front-loaded sentence with zero padding or filler. It is efficient, though its brevity borders on under-specification given the tool's batching behavior.

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?

With no annotations, no output schema, and an undocumented required parameter, the definition leaves too much for the agent to infer. It does not say what the Markdown response looks like for multiple URLs, how partial failures are reported, or what the waitSeconds timeout means in practice.

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 description coverage is only 50%: waitSeconds is documented in the schema, but the required urls array has no description at all. The description implies URLs to HTML pages or PDFs but never mentions the 30-item cap, whether mixing PDFs and web pages in one call is allowed, or what waitSeconds trades off.

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?

States a specific verb (convert) plus the resource (public web pages and PDF links) and the output format (Markdown), which is precise enough to distinguish it from screenshot or sitemap siblings. It stops short of explicitly naming a sibling or the boundary between them, so it is clear but not maximally differentiated.

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 phrase 'for LLM or RAG ingestion' implies the intended use case, but there is no explicit when-to-use or when-not-to-use guidance. The word 'public' hints at an exclusion (no authenticated or paywalled content) without stating it as a constraint, and no alternatives are mentioned.

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