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

Annotations already mark readOnlyHint=true and destructiveHint=false, and the description further explains that it detects expired, self-signed, and weak certificates, and returns a grade. This adds useful behavioral context beyond the annotations, such as its network-based external host checking. No contradiction.

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?

Two concise sentences that front-load the core function, then list key outputs and use cases. Every sentence adds value, and there's no redundancy with the schema or annotations.

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?

With an output schema present and clear annotations, the description need not restate return structures. It provides the essential behavioral and usage context, including what the tool checks, what it returns, and when to use it. This is complete for a tool of this complexity.

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%, with both host and port having clear descriptions. The description reinforces the host parameter by saying 'any HTTPS host' and implies the default port behavior indirectly, but adds no extra parameter details beyond the schema. 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 identifies the action (analyse SSL/TLS certificate) and resource (any HTTPS host), and enumerates specific return values (subject, issuer, validity, grade). This distinguishes it from sibling security tools like security_headers_check or web_security_audit, which target other aspects of web security.

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?

Provides explicit use cases: 'audit TLS posture before production deployment or during security reviews.' It doesn't explicitly contrast with sibling tools, but the focused scope makes the intended usage clear. It would be stronger with an explicit 'for checking HTTP headers use security_headers_check,' but the context is sufficient.

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