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

With no annotations, the description carries the behavioral disclosure burden. It transparently states that the body is discarded and that the URL is public, which is useful. However, it does not mention redirects, rate limits, auth, or other fetch behaviors that would be relevant for a network 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 concise, front-loaded sentences with no filler. 'HTTP status and content type for a public URL' immediately communicates the core behavior, and 'Body discarded' is a useful single-sentence disclosure.

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 semantic gap between the description and the 9-parameter schema is significant: the parameters include refs, cities, feeds, zones, and queries, while the description only describes HTTP status/content type fetching. The description does not explain how these parameters relate to the tool or how to invoke it correctly, which is essential given the parameter count and no output schema.

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 the behavioral note about discarding the body, but it does not clarify the relationship between the 9 optional parameters or explain which parameter should be passed as the URL to fetch.

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 identifies the resource (public URL) and the expected outputs (HTTP status and content type), and adds the important detail that the body is discarded. It is specific and understandable, though it does not explicitly contrast itself with near-neighbor tools like fetch-status.

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?

Usage guidance is only implied: if you need HTTP status and content type for a public URL, this tool may be appropriate. 'Body discarded' hints when not to use it, but no alternative tools or exclusions are mentioned despite many related siblings.

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