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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely useful context beyond them: it opens a network connection to port 443 and reports TLS version, cipher, expiry and SANs, which matters since no output schema exists. It omits failure modes (timeouts, refused connections, self-signed certs), which keeps it short of 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?

A single sentence with the action and the returned data front-loaded, and no filler. Every clause earns its place.

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 does an adequate job naming the returned fields, but it leaves the 'target' value format undefined and gives no tie-breaker against check_tls_configuration. For a one-parameter network tool that is minimum viable rather than complete.

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 0% for the single 'target' parameter. The description refers to an unspecified 'host', which loosely maps to 'target', but it does not say whether an IP, hostname, or URL is accepted, nor that the port is fixed at 443 and cannot be supplied. Partial compensation, not full.

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 gives a specific verb-and-resource pair: connect to a host on port 443 and return TLS version, cipher, and certificate details. That is concrete enough to distinguish it from most siblings, but it never contrasts with the closely named check_tls_configuration, so the boundary between the two is left ambiguous.

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?

The fixed 'port 443' wording implies HTTPS/TLS-on-web usage and implicitly excludes SMTP STARTTLS (check_smtp_starttls) or config-policy inspection (check_tls_configuration), but the description never states when to prefer this tool over those. Usage must be inferred rather than read.

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