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

With no annotations available, the description carries the behavioral transparency burden. It does disclose a key behavior—the response body is discarded—which is valuable context for an agent deciding whether this tool can satisfy a content-extraction request. However, it does not address redirects, failures, timeouts, or the fact that the schema contains many seemingly unrelated optional parameters.

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 extremely concise: two short sentences with no filler. The primary outcome is front-loaded, and the body-discarded caveat is presented immediately. Every word earns its place.

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 description is too thin for a tool with nine optional parameters, no annotations, and no output schema. It does not explain why the schema contains non-URL parameters or clarify which parameter an agent should supply to obtain the HTTP status and content type, leaving room for misinvocation.

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 each parameter is already documented in the input schema. The tool description adds no parameter-level detail, but at this coverage level the schema carries the load, making the baseline 3 appropriate.

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 a concrete observable outcome: HTTP status and content type for a public URL, and it explicitly notes that the body is discarded. This is specific enough to differentiate from content-fetching tools, though it does not explicitly distinguish it from similarly named siblings like fetch-status or browser-url-ok.

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 provides no guidance about when to prefer this tool over alternatives, nor does it mention exclusions. The only implicit signal is that the URL must be public, but this is not developed into a clear when-to-use instruction.

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