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

With no annotations, the description carries the burden well: it discloses the returned fields, the flagging thresholds (expiry < 21 days, TLS < 1.2), and — unusually valuable — the cost and payment mechanism ($0.005 USDC via x402 on Base). Missing: behavior on connection failure/timeout, and confirmation that the check is passive/read-only.

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?

Front-loaded with purpose, then a dense but purposeful enumeration of checks, then pricing. Every clause conveys a distinct check or cost fact; the only mild cost is the long unbroken list, which could be punctuated more crisply.

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?

For a one-parameter read tool with no output schema, the description effectively substitutes for one by naming the result fields and the flag thresholds, and it discloses pricing. Only failure/edge-case behavior and the read-only nature remain unstated.

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?

Single required parameter with 100% schema description coverage ('Hostname, e.g. example.com'), so the schema already does the work. The description adds no extra meaning such as whether a scheme, port, or IP is accepted, so 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 and resource (TLS check on port 443) and enumerates exactly what is examined: protocol, cipher, certificate fields, chain trust, hostname match, legacy TLS acceptance. It is clearly distinct from domainaudit_headers or domainaudit_seo in substance, but it never names or contrasts with domainaudit_audit/audit_bundle, which plausibly overlap with TLS coverage.

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 only implied: an agent infers 'call this when you need TLS/certificate details for a host'. No when-not-to-use guidance, no direction to the bundle or full audit sibling, and no note on prerequisites such as the host needing to serve TLS on 443.

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