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

With no annotations provided, the description carries the full behavioral burden. It implies a safe read-only inspection and lists returned fields, but it does not disclose connection behavior, timeouts, error handling, or whether the check reaches the host directly. Those gaps matter for an agent invoking a network-facing check, though the implied read-only nature limits the risk.

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?

The description is two efficient sentences: the first defines what is inspected and returned, and the second states the use case. There is no redundant or filler content, and the 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?

For a one-parameter tool with no output schema and no annotations, the description is largely complete: it names the key return values and the intended use case. It lacks behavioral details such as timeout or failure modes, but those are minor for a straightforward certificate inspection tool.

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%, and the single `host` parameter is documented in the schema with an example. The description does not add parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 ("Inspect") and resource ("a host's TLS certificate") and names the exact fields returned: issuer, subject, SAN list, expiry date, and days remaining. It clearly distinguishes this from sibling tools such as dns_lookup, http_head, and security_headers, which do not focus on TLS certificate inspection.

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 gives clear usage context: "Use to catch expiring or misconfigured certificates." That tells the agent when the tool is relevant, but it does not name alternatives or state when not to use it, so it falls short of explicit routing guidance.

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