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

No annotations are provided, so the description must carry the full burden. It describes a network operation ('Fetch live') but does not disclose latencies, failure modes (e.g., unreachable host, timeout), or whether it might be blocking. This is insufficient for an agent to anticipate side effects.

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 conveys the core action and key outputs with no extraneous words. It is well 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?

Given no output schema, the description hints at return fields (expiry, issuer, SAN) but does not specify the structure (e.g., whether a full certificate object or just those fields). For a tool that likely returns structured certificate data, more detail on the output format would improve completeness.

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%, so the description must compensate. It mentions 'host:port' but does not clarify that 'host' is required and 'port' defaults to 443, nor explain constraints (port range). The parameter names are self-explanatory, but additional detail would reduce ambiguity.

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 ('Fetch') and resource ('live TLS certificate'), and lists key data points (expiry, issuer, SAN). It clearly distinguishes from siblings like dns_lookup (DNS records) or x509_parse (parsing a PEM string).

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 description implies usage for retrieving current certificate details from a live host, but lacks explicit guidance on when to use vs. alternatives (e.g., x509_parse for existing certificates) or when not to use (e.g., if offline). No context on prerequisites or limitations.

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