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

With no annotations, the description carries the full burden. It only states that the body is discarded, which is a minor behavioral detail. It does not mention network access, side effects, permissions, or how the various parameters are handled. The description is silent on most behaviors, leaving the agent to guess.

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 only two sentences, which is very concise, but it is under-specified for a tool with 9 parameters and no output schema. It lacks structure, such as grouping parameters or explaining the tool's overall function. This is under-specification rather than effective conciseness.

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, none required, and no output schema. The description only mentions HTTP status and content type for a URL, but provides no explanation of what happens with the other parameters or what the output format is. An agent cannot determine how to invoke this tool correctly for most of the parameters.

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%, and each parameter has its own description in the schema (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no parameter-level detail beyond what the schema already provides. Baseline 3 applies since the schema does the heavy lifting, but the description does not clarify the overall relationship between the URL-focused description and the other parameters.

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 it returns HTTP status and content type for a public URL, which is specific, but it entirely ignores the 8 other optional parameters in the schema (city, json, path, zone, query, etc.). This creates a misleading impression that the tool only handles URLs, when the schema suggests it accepts many unrelated inputs. It does not distinguish from sibling tools like fetch-status or normalize-url.

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?

No guidance on when to use this tool vs the many siblings (fetch-status, browser-url-ok, normalize-url, etc.). The description does not state any prerequisites, exclusions, or context that would help an agent choose it over alternatives.

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