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

Annotations already declare readOnlyHint and openWorldHint, so the outbound-network nature is covered; the description adds genuinely new context: the $0.05-style paid model (x402 / USDC on Base per call), the 14/30-day expiry thresholds used for flagging, and the specific anomaly classes (missing certs, failed handshakes, very new certs, mixed issuers). It does not detail failure/error payloads, which would be needed for a 5.

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 purpose is front-loaded in the opening clause and the sentence is dense but organized: check type, data sources, returned fields, flag thresholds, use case, price. It is long for a single sentence but nearly every clause adds distinct information.

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 must explain what comes back, and it does — reachability/status/HSTS, issuer, validity window, days left, covered names, wildcard, other active certs, and the flag conditions. Combined with the disclosed per-call cost, an agent has everything needed to decide and invoke.

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?

There is only one parameter and the schema documents it at 100% coverage with an example, so the description carries no additional burden. It implies the host is a resolvable domain rather than a URL, but that nuance is not spelled out beyond the schema's own example.

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 names a specific verb and resource ('TLS/SSL certificate check for a host') and enumerates the two data sources — a live verified HTTPS handshake and Certificate Transparency logs — which clearly separates it from sibling tools like domain_dns, domain_whois, and web_security_headers.

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?

'Use for uptime/expiry monitoring or to vet a site' gives concrete intended use cases, so an agent knows the triggering scenario. It stops short of naming alternatives or exclusions (e.g., when domain_overview or web_security_headers is the better pick), which keeps it below a 5.

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