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

No annotations are provided, so the description carries the full burden. It implies a read-only network probe and discloses the returned fields, but says nothing about timeouts, failure/connection-error behavior, rate limits, or whether the check follows redirects or validates chains. For a simple connectivity check this is adequate but not rich.

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?

Two tight sentences: the first states what it does and what it returns, the second carries the disambiguation. Nothing is padded and the core purpose is front-loaded.

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 enumerates the return fields, and it routes the agent to the sibling for deeper analysis. Minor gaps remain around error/timeout behavior, but for a two-parameter read-only check the description is nearly 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 100%, so the schema already documents both hostname and port (with default 443). The description's 'Connect to a host' restates the hostname parameter but adds no format or syntax detail beyond what the schema provides. 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 (connect over TLS) and resource (the host's certificate), then enumerates the exact fields returned (expiry date, days remaining, issuer, subject). It explicitly distinguishes itself from the sibling ssl_labs_grade, so an agent can route between them without opening either schema.

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?

Gives explicit when-to-use (quick 'fast facts' about a cert) and when-not ('for a full graded TLS assessment (protocols, ciphers, vulnerabilities)') and names the alternative tool by name. There is no ambiguity about which of the two TLS tools to pick.

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