ssl_inspector__inspect_ssl

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

No annotations are provided, so the description carries the full burden. It does not disclose permission requirements, rate limits, or that it performs live network handshakes (implied by probes/checkHsts defaults). For a tool that initiates external connections, this is a significant gap.

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, well-formed sentence with the key scope constraint ('for a single domain') front-loaded and no extraneous content.

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 tool that makes outbound network connections with no annotations and no output schema, the description is incomplete: it omits safety/permission context, expected output, and any guidance on how this differs from the four sibling ssl_inspector tools. More is needed.

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%, so the schema already documents host, port, probes, and checkHsts in detail. The description adds no parameter-level semantics beyond what the schema provides. Baseline 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 states a specific verb (Inspect) and resources (TLS certificate, cipher suite, protocol configuration) scoped to a single domain. It is clear and specific, though it does not explicitly differentiate itself from sibling tools like inspect_ssl_bulk, check_cert_expiry, or get_cert_info.

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?

It says 'for a single domain,' which implies usage context, but there is no explicit when-to-use guidance or statement of when to prefer siblings like inspect_ssl_bulk (for multiple domains) or check_cert_expiry (for expiry-only checks). Usage must be inferred.

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