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

No annotations are provided, so the description carries the burden. It usefully discloses that the call is synchronous and waits for all checks to complete (implying a potentially slow blocking call), and the schema's force parameter hints at caching. But it omits auth requirements, failure/timeout behavior, and what the rating means.

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 dense sentence front-loads the purpose and lists the checked dimensions with zero filler; the synchronous-wait note is appended efficiently. Slightly list-heavy but well-structured.

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 no annotations and no output schema, the description must convey behavior, and it partially does (scope + blocking semantics). It leaves out what the result contains (rating scale, per-check breakdown) and any error handling, which an agent needs for a multi-check inspection tool.

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 host, port and force are already documented with FQDNs, port fallback and cache-skip semantics. The description adds no parameter-level detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb+resource (HTTPS 体检) and enumerates exactly what is inspected: TLS/TLCP, RSA/SM2 certs, root trust, chain OCSP/CRL, protocol suites and rating. An agent can tell this is a full endpoint TLS assessment, distinct from the decode/match siblings, though no sibling is named.

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?

Usage is implied by the scope (inspect a live HTTPS host), but there is no explicit when-to-use vs cert.decode/cert.match, no prerequisites, and no statement about hosts that are unreachable or non-HTTPS. The agent must infer the selection condition.

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