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

With no annotations, the description carries the full burden. "Inspect" implies a read-only, non-destructive probe and the field list reveals what is surfaced, but nothing is said about error behavior for unreachable hosts, expired/self-signed certificates, chain-following, or timeouts.

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 sentences, front-loaded with the operation and the inspected fields, then the one useful default. No filler, and every clause carries information.

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?

The enumerated field list usefully compensates for the absence of an output schema, and the default port is stated. However, for an unannotated network tool it omits failure modes and any hint about result shape or timings, leaving the agent to guess at edge-case behavior.

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 50%: host is documented in the schema ("Hostname, no scheme") and port has bounds and a default. The description adds only the port default, which merely restates the schema, and does not clarify port semantics for non-443 services or what happens if TLS is not negotiated.

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?

"Inspect the SSL/TLS certificate of a host" gives a specific verb and resource, and the follow-on list (chain, protocol, cipher, expiry, SAN list) makes the scope concrete. It does not explicitly distinguish itself from near siblings like check_protocol or check_security, but the certificate focus is unambiguous.

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 by the resource: an agent can infer this is for verifying a host's TLS certificate. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as check_http or check_protocol, and no mention of prerequisites (reachable host, open port).

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