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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the body is discarded, which is a useful behavioral trait. However, it omits other important details like whether redirects are followed, timeouts, authentication requirements, or rate limits. It adds some value but is not comprehensive.

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 a single, concise sentence that front-loads the core purpose ('HTTP status and content type'). It is efficient with no wasted words. However, it may be too brief, sacrificing completeness for brevity.

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?

Given the tool has 9 parameters and no output schema, the description is insufficiently complete. It does not explain how the many parameters (ref, city, feed, host, json, path, zone, query) fit into the tool's operation or whether the tool handles multiple check types beyond URL status. The description only covers the URL case, leaving agents uncertain about the other parameters and the expected response format.

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?

The schema descriptions cover 100% of the parameters, so the baseline is 3. The tool description adds no additional meaning about how the parameters relate to the tool's behavior; it only mentions 'URL' while the schema lists 9 parameters with varied purposes. The description does not help clarify which parameter is relevant for the primary function.

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 the tool returns HTTP status and content type for a public URL, and that the body is discarded. This is a specific verb+resource outcome. However, it does not differentiate from sibling tools like fetch-status or browser-url-ok, leaving the agent to infer which one to use.

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 is given on when to use this tool versus alternatives. There is no mention of scenarios where this should be chosen over fetch-status, normalize-url, or other siblings. The agent is left to infer usage from the minimal description.

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