health_check

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

Annotations already declare the operation is read-only, idempotent, and non-destructive, so the safety profile is known. However, the description adds no behavioral context beyond the name: it does not clarify what 'responds' means (e.g., any HTTP status vs. only 2xx), timeout behavior, redirect handling, or whether a valid HTTP response still counts as failure. These are meaningful behavioral ambiguities left to the caller.

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 with no filler. The key action and resource are front-loaded, and every word contributes to the core meaning. It is appropriately sized for a simple tool.

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 there is no output schema, the description should specify what 'report whether it responds' returns (e.g., a boolean, JSON, or status code). It also lacks any guidance for distinguishing this from sibling network probes, leaving an agent without enough information to select and use the tool correctly in practice. The simple structure mitigates the gap, but the missing return format and usage context make it incomplete.

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% and the only parameter, 'url', has no schema description. The description does slightly compensate by specifying that the URL must be an HTTP(S) URL, but it does not explain the expected format (e.g., full URL with scheme, whether paths and queries are allowed, or whether scheme is optional). This is minimal value beyond the parameter name.

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 ('probe'), a resource ('an HTTP(S) URL'), and an outcome ('report whether it responds'). It is clear and unambiguous, but it does not explicitly differentiate itself from sibling tools like ping_host or check_port, which also probe network endpoints.

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 offers no guidance on when to use this tool versus alternatives. It does not mention that ping_host is ICMP-only, check_port tests TCP ports, or that this tool is appropriate for checking web server availability over HTTP(S). An agent must infer the use case solely from the name and description.

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