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

Annotations already establish read-only/idempotent behavior; the description adds useful behavioral detail by disclosing the default output form (decoded raw body) and the render mode switch. It does not discuss cost/rate limits, but that is not required given the strong annotation coverage.

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?

Three tight sentences front-load the action, then give the mode-switching condition and a concrete call example. There is no filler or redundant framing.

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 three-parameter read-only fetch with 100% schema coverage, the description provides enough to call it correctly and know what to expect back. It omits failure/error behavior, but the low complexity and annotations make that a minor gap.

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%, so the schema already documents url, render, and _apiKey fully. The description restates render's effect and shows a call example, but adds little semantic detail beyond what the schema examples already provide.

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 action (fetch a web page via Zyte API) and clarifies the return: raw HTTP response body by default, browser-rendered HTML with render:true. That is specific enough to tell zyte_fetch apart from the sibling data-extraction (zyte_extract) and screenshot tools, even without naming them.

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?

It gives clear, actionable guidance on when to set render:true ('JS-heavy sites that need a real browser'), which is the main mode decision. It does not explicitly position zyte_fetch against zyte_extract or zyte_screenshot, so it stops short of full alternative-sibling guidance.

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