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

With no annotations, the description carries the full burden and does disclose meaningful traits: a single HEAD request only, SSRF-safe execution, operator authorization requirement, no paid crawler triggering, and an explicit $0.001 USDC x402 cost on Base. These are non-obvious behavioral facts, though it omits auth mechanics and return behavior.

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?

A single dense sentence with the core action and the key safety/cost constraints front-loaded. It is efficient, though the clause stacking ('using SSRF-safe existing gateway HTTP tooling') is slightly compressed.

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?

With no annotations and no output schema, the description covers the important safety and cost dimensions but never says what the HEAD request returns or how a 'health' result is surfaced. For a paid, safety-sensitive tool this leaves a notable gap in the calling contract.

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 0%, so the description must compensate. It loosely maps to both params ('public supplier endpoint' for url, 'operator-authorized' for operator_authorized), but adds no format, validation, or semantics beyond the bare names, leaving some interpretation work to the agent.

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 specific verb (HEAD request) and resource (public supplier endpoint) with a clear scope ('one', 'operator-authorized'). It is distinguishable from siblings like canonical-web-scrape, http-status, and http-headers-security, though it never explicitly frames itself as a health/availability check as the name implies.

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?

Usage is implied through constraints like 'operator-authorized' and 'no paid crawler triggering', which hints at when this is preferred over crawler tools. However, it never names an alternative (e.g., http-status, http-headers-security) or states explicit when-not-to-use conditions.

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