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

With no annotations, the description carries the burden, and it does disclose one real behavioral trait — the check is 'Free' — plus the hard scope limit of port 443. It does not say whether the call is a live network lookup, what happens on connection failure or timeout, or whether a validation failure is returned as data rather than an error, which matters for a network probe.

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 dense sentence front-loads the resource and then the returned fields; the one-word 'Free.' sentence earns its place as a cost signal. Nothing is padded.

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?

There is no output schema, so the description must describe return values, and it does so compactly (validates, issuer, names covered, expiry, days left). The remaining gap is failure/error behavior for unreachable or non-TLS hosts, which is minor for a simple one-parameter lookup.

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% and there is only one parameter, so the schema already documents 'host' including a format example. The description adds only the implicit constraint that the host is probed on port 443; it adds no format or edge-case guidance beyond the schema, so the 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?

The description names the concrete resource (the TLS certificate served on port 443) and enumerates what is reported: validation result, issuer, covered names, expiry and days left. That is far more specific than a tautology and clearly separates it from siblings like check_blocklists or inspect_domain_dns, though the verb itself is implicit rather than stated.

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 only implied: an agent can infer it should call this when it needs certificate/expiry data for a host. There is no explicit when-to-use, no note about what it does not cover (e.g. non-443 ports, STARTTLS on mail servers, which several email-focused siblings might imply), and no named alternative.

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