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

With no annotations, the description itself must disclose behavior, but it only says 'check' without explaining what is inspected, what output is returned, whether network access is required, or any caveats. It implies a read-only inspection but provides no substantive behavioral detail.

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 extremely short and easy to parse, with the core purpose front-loaded. The 'SSL Check:' prefix is somewhat redundant with the tool name, keeping it from a 5.

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 tool has no annotations, no output schema, and two optional-looking parameters, yet the description only covers the basic purpose. It leaves unresolved the host-vs-domain distinction, expected return content, and any operational behavior, so an agent cannot invoke it with confidence in novel situations.

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%, which meets the baseline of 3. However, both parameter descriptions are generic ('Host to process', 'Domain to process') and do not clarify whether both are needed, how they differ, or which one is authoritative for the certificate check.

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 clear action and resource: 'Check a domain SSL certificate.' This is specific enough for basic comprehension. However, it does not distinguish this tool from overlapping siblings such as cert-expiry, domain-expiry, tls-version, or hsts-check.

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?

No guidance is provided about when to use this tool rather than alternatives, and no exclusions or conditions are mentioned. Given numerous certificate/TLS-related siblings, the lack of routing context leaves the agent to guess.

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