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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully pins the connection to port 443, which tells the agent no port parameter is needed and that a live handshake is performed. It omits operational behavior an agent would want: timeouts, handling of expired/self-signed/unreachable hosts, and whether a failed handshake errors or returns a report.

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 well-formed sentence with the action and the target port front-loaded and the return fields listed after. No filler. Minor redundancy between "certificate chain" and the trailing "chain details".

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 one-parameter read-only tool this is largely sufficient: the action, transport, and return contents are all covered, and annotations carry the safety profile. No output schema exists, yet the description lists the returned fields, which fills that gap. Failure modes and expected input format are the remaining holes.

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 one parameter at 100% schema coverage, but the schema text is only "Domain (Enter domain)", which adds nothing. The description partially compensates by implying a bare hostname reached on port 443, i.e. no scheme, path, or port should be supplied. It does not state whether subdomains, wildcards, or IP addresses are accepted.

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 uses a specific verb+resource pair ("Connect to a domain on port 443 and report the certificate chain") and enumerates the exact fields returned (subject, issuer, validity dates, days remaining, SANs, chain details). An agent can tell this is a live TLS handshake check rather than a DNS/CAA/CT-log lookup. It stops short of naming a sibling such as port_check or certificate_transparency_search, so differentiation is inferential.

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?

Usage is implied rather than stated: the mention of "days remaining" signals expiry monitoring, and "port 443" signals a live-endpoint requirement. There is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives like certificate_transparency_search for historical/log-based cert data. An agent can guess the context but must do the routing work itself.

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