Tls Certificate Check

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

No annotations are provided, so the description carries the full burden, yet it discloses almost nothing beyond the one-line purpose: not that it opens a network connection, whether it is read-only and non-destructive, what happens on handshake failure or timeout, or whether it validates trust chains. For a network-facing diagnostic tool with zero annotation coverage, this is a meaningful gap.

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 front-loaded sentence with no filler; nothing needs to be cut. It is arguably under-specified rather than concise, but there is no structural waste.

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 should explain what the inspection yields (expiry, issuer, subject, SANs, chain validity) and failure behavior. None of that is present, leaving the agent unable to predict results or error semantics.

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, port, and timeout all documented including defaults, so the schema does the heavy lifting. The description adds no additional parameter meaning (e.g. whether port accepts non-standard TLS ports or what timeout applies to). Baseline 3 applies.

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 ('Inspect') and resource ('TLS certificate presented by a host'), which is unambiguous and clearly distinct from siblings like curl_request, ping_host, or dig_query, none of which inspect certificates. It stops short of 5 because it doesn't explicitly name the neighboring tool it might be confused with (e.g. telnet_connect or curl_request) to reinforce the boundary.

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 guidance on when this tool should be chosen over alternatives such as curl_request or telnet_connect, nor any preconditions (e.g. the host must be reachable, port defaults to 443). The agent must infer all selection logic.

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