http_check

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

With no annotations, the description carries the full burden, and it does disclose the outputs (status code, response time), which is valuable given there is no output schema. However, it omits timeout behavior, redirect following, whether the body is downloaded, and any failure-mode or rate-limit context an agent would want before probing an endpoint.

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?

Two sentences plus a single-argument block, front-loaded with what the tool does and immediately followed by the parameter detail. No padding or repetition.

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?

For a single-parameter diagnostic with no output schema and no annotations, the description covers purpose, the returned values, and the scheme default. It is close to complete; only timeout/redirect/error behavior is left to be discovered at runtime.

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 coverage is 0%, so the description must compensate, and it does: it gives an example value and, critically, the default behavior that 'https is assumed if no scheme is given'. That is exactly the kind of semantic the bare `string` schema does not convey.

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?

States a specific verb and resource ('Request a web page's headers') plus the two outputs ('HTTP status code and response time'), which is far more precise than a bare name. It implicitly separates itself from the raw-network siblings (ping, traceroute, port_check) by being an application-layer HTTP probe, though it never names an alternative.

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 usage is only implied by the purpose: an agent can infer this is for checking whether an HTTP endpoint responds and how fast. There is no explicit 'use this instead of port_check when...' or 'use when you need an application-layer response rather than TCP reachability', and no exclusions or prerequisites.

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