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

With no annotations, the description carries the burden and does disclose one important behavior: the body is discarded. It does not mention redirects, timeouts, or how the many other schema parameters are treated, so behavioral coverage is partial but not misleading.

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, purposeful sentences. The main output is front-loaded and the critical side-effect ('Body discarded') is stated without any fluff 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?

The tool has 9 optional parameters, no annotations, and no output schema, yet the description only covers one use case. It does not explain whether only 'url' is used, whether other parameters are ignored, or what happens on error, leaving an agent under-equipped to call this correctly.

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 baseline is 3. The description adds little beyond the schema—it only mentions 'URL', which maps to the 'url' parameter, but leaves the other eight parameters' relevance unclear. The schema itself documents them, so no severe penalty.

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 clearly states a specific verb and resource: fetch a public URL and return HTTP status and content type. However, it does not differentiate from sibling tools like fetch-status or browser-url-ok, so it stops 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?

The phrase 'public URL' implies when this tool is appropriate, and 'Body discarded' suggests not to use it if the response body is needed. Yet it gives no explicit alternatives, exclusions, or comparison to sibling tools, leaving usage largely implied.

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