tls_inspect

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

With no annotations provided, the description carries the behavioral burden and does this well by stating that it makes a live connection, reports the certificate actually served, and refuses private/reserved addresses. It does not discuss edge cases like timeouts or whether the connection performs full validation, but it discloses key operational behavior.

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 sentences with no filler. The first sentence front-loads the tool's outputs, and the second sentence adds port and host constraints. Every clause adds useful 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?

There is no output schema and no annotations, yet the description fully enumerates the returned certificate data and the main input constraints. An agent can predict what the tool does, what it returns, and when it refuses to operate, making the definition complete for this complexity level.

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%: host and port are already documented in the schema. The description adds minor reinforcement ('Accepts a URL', 'Any port default 443') but does not materially expand parameter meaning beyond the schema.

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 a specific verb ('Connect') and resource ('TLS certificate'), then enumerates exactly what it reports. It is clearly distinct from sibling network tools like dns_lookup, reverse_dns, or lookup_port because only this one inspects live TLS certificates.

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 makes the intended use clear: connect to a public host and inspect its served certificate. It also specifies that private or reserved addresses are refused, which helps the agent know when the tool will not work. It does not explicitly name alternative tools, but the context is sufficient for selection among the siblings.

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