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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates the single-hostname constraint, which is a useful behavioral trait, but it does not disclose the return format, whether the full trust chain is inspected, failure modes, or any potential side effects. For a read-only inspect operation this is acceptable but not thorough.

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 tight sentences: the first states the core function and scope, the second routes to alternatives. Every word earns its place, and the most critical constraint ('ONE hostname only') is front-loaded. No redundancy or 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?

For a simple single-parameter tool with no output schema, the description covers the core purpose, scope, and when not to use it. It could mention what the response contains (certificate details, expiration, issuer) but the tool name and purpose make that largely inferable. The main missing piece is parameter format guidance, already penalized in parameter semantics.

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 0%, so the description must compensate. It adds only the constraint of 'ONE hostname' but does not clarify acceptable formats (e.g., bare domain vs. URL-with-scheme, whether ports are allowed). An agent could plausibly pass 'https://example.com/path' because the format is not specified. This is a real gap given the low schema coverage.

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 uses a specific verb ('Inspect') and resource ('TLS certificate') and explicitly limits scope to 'ONE hostname only.' This clearly differentiates it from sibling tools like get_dns_lookup or get_security_headers, which target different resources. The purpose is unambiguous and immediately actionable.

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 description explicitly states when to use this tool vs alternatives: 'For TLS combined with HTTP headers and DNS, use /web/audit (raw) or /security/posture (scored).' It names concrete sibling tools and the exact condition that should route an agent away from this tool. No inference is required.

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