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

With no annotations, the description must carry all behavioral disclosure, but it only states that it performs a HEAD request and returns a status. It does not disclose that many parameters are discarded after a 'shape check,' that some checks may not involve network calls, or what the returned status actually means. Minimal and insufficient.

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 short sentence, which is concise but drastically under-specified for a tool with 9 parameters and numerous siblings. It lacks structure or any informative breakdown, so it does not earn the conciseness credit.

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's complexity (9 parameters, 28 siblings), the description is woefully incomplete. It does not explain the general purpose (a multi-input shape checker), how to choose among parameters, what 'status' refers to, or any error conditions. An agent cannot reliably use this tool based on this description.

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%, and each parameter has a brief description (e.g., 'Git ref name; discarded after the shape check'), which adds some meaning. However, the tool description does not tie the parameters together or explain how they relate to the stated HEAD operation, so the description adds little beyond the schema.

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 'HEAD a public URL and return status only,' which is a clear action for the URL case, but the input schema lists 9 unrelated parameters (city, json, path, zone, etc.) that are not mentioned. This is misleading because an agent would assume the tool only works on URLs, yet it accepts many other input kinds, making its actual purpose ambiguous.

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 its many siblings (browser-url-ok, validate-json, normalize-url, etc.). There is no mention of alternatives, conditions, or exclusions, leaving the agent to guess which tool fits a given request.

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