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

Annotations already cover read-only/idempotent/open-world, but the description adds materially new behavioral facts: a per-call price ($0.01 USDC via x402 on Solana) and a parallel HTTPS endpoint. It does not describe failure modes (unreachable host, untrusted chain) or whether a failed call is still billed.

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?

Front-loaded with the core action and the return payload, so the essential information comes first. The one long enumerative sentence plus two terse fragments are efficient, though the field list is dense enough to slightly blur the priority of the port/pricing constraints.

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 correctly takes on the burden of describing the return payload in detail, including chain trust and hostname matching. Pricing and transport details are covered; only error/edge-case behavior is missing.

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 100%, so the schema already documents host parsing and the port list; the description largely repeats the same port enumeration and the 'host extracted' behavior. Baseline 3 applies since no additional semantics (default resolution order, SNI-vs-IP caveats) are added beyond the schema.

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?

Opens with a specific verb+resource ('Inspect a live TLS certificate') and enumerates the exact fields returned (subject, issuer, SANs, chain, cipher, RFC 6125 match), which clearly separates it from siblings like ssl_blacklist, ct_subdomains, and headers_audit.

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?

It states the eligible implicit-TLS ports, which implies when the tool applies, but it never names an alternative or an exclusion condition (e.g., 'use ssl_blacklist for reputation' or 'use ct_subdomains for historic certs'). The agent must infer routing from the port list alone.

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