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

With no annotations, the description carries the full burden and does well: it discloses 'a benign TLS handshake plus a keyless HSTS lookup — no probing' and 'Read-only', covering the network-touch and safety profile. It also explains what raises and lowers the grade. It omits rate limits or auth requirements, keeping it short of a 5.

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?

Three sentences, front-loaded with the core purpose before the factor details and behavioral note. Dense but essentially waste-free; the parenthetical lists of factors are informative rather than filler.

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?

There is no output schema, but the description explains the return values (letter grade, 0–100 score, contributing factors) so an agent knows what to expect. Combined with the read-only/no-probing disclosure, it is nearly complete for a two-parameter read tool; only auth/rate-limit context is absent.

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% and both parameters (host, port with default 443) are fully documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the 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?

States a specific verb (grade), resource (host's transport security), and output form (A–F letter grade) in the first clause. It distinguishes itself from siblings by naming exactly which tools it aggregates: tls_certificate, cert_revocation, and hsts_preload_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?

The phrase 'in one call' plus the explicit correlation of three sibling tools strongly implies this is the aggregator to use instead of calling tls_certificate/cert_revocation/hsts_preload_check separately. It lacks an explicit 'use this when... instead of...' exclusion, but the routing intent is clear.

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