check_ssl

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

Beyond the readOnly/idempotent annotations, the description discloses a crucial behavioral nuance: certificate data comes from public Certificate Transparency logs and may differ from the currently served certificate. It also explicitly states what is NOT returned (negotiated TLS versions/cipher suites), preventing agent misinterpretation.

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 compact, front-loaded with purpose, and every sentence contributes value. It combines scope, output expectations, a key pitfall, limitation disclosure, and usage guidance with no fluff.

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?

Given an output schema exists and the annotations cover safety, the description still provides a complete operational picture: what is checked, where data comes from, a meaningful caveat, and explicit limitations. The agent can both select and invoke the tool confidently.

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 100% and all parameters already have meaningful descriptions, including the enum for format and force_refresh behavior. The description adds high-level context but does not need to repeat parameter syntax, so 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 clearly states a specific action and resource: 'Check the HTTPS/TLS posture of a domain' with concrete sub-checks like HTTPS reachability, HSTS policy, redirects, and certificate metadata. This distinguishes it from sibling DNS/security checks and makes immediate sense to an agent.

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 explicitly says 'Use to verify HTTPS/HSTS configuration and certificate issuer/expiry' and notes it is 'Part of the scan_domain audit.' It lacks explicit exclusion or alternative-tool guidance, but the stated use cases are clear enough for selection.

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