fetch_content

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

With no annotations, the description carries the full burden, and it does add real value by disclosing the retrieval pipeline and its fallback behavior (Jina Reader, Exa fallback). However, it says nothing about failures, paywalls, private/authenticated pages, rate limits, or truncation limits — significant gaps for a network fetch tool.

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?

Two short sentences, front-loaded with the action and output format, with zero filler.

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 output schema, the description compensates by specifying the return shape (title, url, published_at, text) as a unified envelope item. The parameter is self-evident, so the main remaining gap is failure/edge-case behavior, which is a modest omission.

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 single parameter is named 'url' with 0% schema description coverage; the description implies it accepts a web page address but adds no format constraints (absolute URL, scheme, redirects). Marginal value over the schema.

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 and resource ('Read a web page as clean markdown'), which distinguishes it functionally from the sibling 'search' (find vs. fetch). It does not explicitly name the sibling or state the relationship, so it falls short of a 5.

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?

There is no when-to-use or when-not guidance, no mention of the 'search' sibling as the way to obtain a URL, and no prerequisites. Usage is only inferred from the verb 'read'.

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