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

Annotations already convey readOnlyHint and openWorldHint, and the description does not contradict them. It adds meaningful behavioral context beyond those: a fresh browser per request, Alpha maturity, API-key auth requirement, and the fact that returned status_code comes from the site. No rate-limit or failure-mode disclosure, but annotations lower the burden.

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 dense sentences front-load the core action and output options, then add the most useful parameter hints and caveats. Every clause contributes; there is no filler or repetition of schema details.

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 13 parameters and no output schema, the description covers the essential output shape, the main output-format parameter, content-narrowing parameters, auth, and maturity. It does not cover every edge case, but combined with the parameter descriptions in the schema it is sufficient for correct invocation.

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 100%, so the baseline is 3. The description adds value by mapping output formats to respond_with, mentioning the default format, and explaining target_selector/remove_selector for narrowing content. This goes beyond the bare schema descriptions and helps an agent choose parameters correctly.

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?

Description uses a specific verb ('Render') and resource ('one public web page') and details return formats (Markdown, HTML, text, screenshot) and fields (url, title, content, status_code). This clearly separates it from sibling search tools, which return search results rather than fetching a known page.

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 implies usage by describing what the tool does, but it never explicitly says when to prefer web_fetch over the sibling search tools. It adds useful constraints—'public web page', 'Alpha', and 'Requires an API key'—but stops short of naming alternatives or exclusion conditions.

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