ssl-cert

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

No annotations are provided, so the description carries the burden. It describes the output fields but does not mention behavioral traits such as being read-only, requiring no authentication, or potential side effects (none expected). It could be more explicit about the tool's non-destructive nature and any rate limits or network dependencies.

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 long, front-loaded with the primary purpose, and efficiently lists all return fields and use cases. Every sentence earns its place, and there is no redundant 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 description covers the tool's purpose, parameters, and return values comprehensively for its complexity. There is no output schema, but the description compensates by listing key output fields. Could mention error handling or timeout behavior, but overall it is sufficient for an agent to use correctly.

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% with descriptions for all three parameters (host, port, servername). The description adds value by explaining the 'servername' parameter's use case (SNI override when connecting to IP with multiple domains). This provides context beyond the schema's basic definition.

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 the tool inspects TLS/SSL certificates, lists specific return fields (validity window, issuer, subject, SAN, fingerprint, serial, expiry status), and states use cases (monitoring expiry, auditing, verifying SAN). This distinguishes it well from sibling tools, none of which directly perform SSL inspection.

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 mentions three use cases (monitoring certificate expiry, auditing TLS configuration, verifying SAN coverage) but does not explicitly state when not to use this tool or compare it to alternatives. Given the sibling list contains no similar tools, the implied usage is clear, but explicit guidance is lacking.

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