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

With no annotations provided, the description carries the full behavioral burden. 'Inspect' signals a read-only operation, and 'public hostname' hints at a live network lookup, but the description does not disclose potential failure modes, latency, dependency on external network access, or what happens for hosts without a valid certificate.

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 a single, front-loaded sentence with no filler. Every word earns its place, and the key scoping constraint ('public hostname') is included without adding unnecessary detail.

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 single-parameter tool with no output schema, the description gives enough to identify the tool and invoke it with a hostname, but it does not explain what certificate information will be returned (e.g., issuer, expiry, chain). Because no output schema or annotations exist, a slightly richer description would have made the tool more self-sufficient.

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?

The schema provides only a 'Hostname' title for the single required parameter, with 0% schema description coverage. The description adds useful meaning by specifying that the hostname must be 'public,' but it does not clarify format expectations such as whether to include a protocol, port, or path, leaving partial 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 states a specific action ('Inspect') and a specific resource ('SSL/TLS certificate information'), scoped to 'a public hostname.' This clearly differentiates the tool from siblings like get_dns_lookup, get_security_headers, and get_security_posture without needing to open their schemas.

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 phrase 'for a public hostname' implies the tool is intended for publicly reachable hosts, but the description does not explicitly state when to prefer this tool over alternatives or when not to use it. There are no exclusions or sibling-tool routing cues, so usage context is only implicit.

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