fetch_url

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds meaningful behavioral detail: it uses Jina Reader, handles JS rendering and bot detection, and returns readable markdown text. This goes beyond the schema and annotations without contradicting them.

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 three concise sentences, each serving a purpose: declaring the core function, explaining the underlying mechanism, and listing suitable use cases. There is no filler or 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?

For a single-parameter tool with annotations and an output schema, the description is sufficiently complete. It covers the intended use, the behavior of the underlying reader, and the return format, leaving no critical gap for an agent deciding to invoke it.

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 100%, with the 'url' parameter described as 'HTTP(S) URL to fetch.' The description adds little beyond this, only generalizing to 'any URL,' so it provides no significant additional parameter semantics beyond the schema baseline.

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 states a specific verb and resource: 'Fetch any URL and return clean markdown content.' This clearly differentiates fetch_url from the search-oriented siblings by describing a direct retrieval action on an explicit input.

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 clear context, noting it is 'Ideal for reading articles, papers, docs, or blog posts,' and explains that Jina Reader handles JS rendering and bot detection on the user's behalf. It does not explicitly name alternative tools or state when not to use it, but the contrast with search siblings is implicit.

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