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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety and outbound-network behavior are covered structurally. The description usefully adds what the call actually retrieves over the wire (cert fields, TLS version, HTTP/2), but is silent on failure modes an agent will hit — refused connections, expired or self-signed certificates, and timeouts.

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?

One tight sentence with the action front-loaded and the returned fields enumerated in a compact parenthetical. No filler and nothing buried.

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 output schema, the description carries the burden of describing the return shape and does so by listing subject, issuer, validity, SAN, TLS version, and HTTP/2 support. For a two-parameter read-only probe this is nearly complete; only error and timeout behavior is unaddressed.

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%, with host and port both documented in the schema, so the baseline is 3. The description adds no additional parameter meaning such as accepted host formats, SNI behavior, or port-specific handling.

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 concrete verb and resource: 'Connect over TLS and report the certificate...TLS version and HTTP/2 support.' An agent immediately knows this performs an active TLS handshake and enumerates the result. It does not distinguish itself from the sibling http_check, which is a plausibly overlapping network probe.

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?

There is no when-to-use guidance, no when-not, and no mention of the sibling http_check that performs a related check. Usage is only implied by the tool's name and the type of data returned.

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