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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Body discarded' and mentions HTTP status/content type, but does not describe the return format, error behavior, permissions, or rate limits. This is minimal and insufficient for a tool with zero annotation support.

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?

The description is two sentences, front-loads the core purpose, and contains zero unnecessary words. It is appropriately sized for the stated function, even if the function is incomplete.

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 parameters, no output schema, and no annotations. The description does not explain why there are so many unrelated parameters (city, feed, zone, query, etc.), what the return value looks like, or any edge cases. This is a significant gap for an agent to call the tool 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 main description adds no parameter context, and while the schema describes each parameter, those descriptions are cryptic (e.g., 'discarded after the shape check') and do not explain their relevance to the stated purpose. The description adds no value beyond the schema, but the schema itself is present.

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 it returns HTTP status and content type for a public URL, which is a specific verb and resource. However, it does not explicitly distinguish from sibling tools like fetch-status, which likely serves a similar purpose, so it loses a point for lack of differentiation.

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 gives no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions. Given there are many sibling tools with overlapping names (fetch-status, browser-url-ok), an agent has no help deciding which to invoke.

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