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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations by naming the external source (crt.sh), stating the output fields, and noting deduplication of subdomains across CT entries. It stops short of caveats like data freshness or pagination, but this is sufficient for a read-only lookup.

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 compact, front-loaded with the core function and source, and each sentence earns its place. Use cases are deferred to the end, keeping the most operationally relevant information first.

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 description conveys the tool's purpose, external source, and main output components, and the schema documents the required domain and optional limit. However, with no output schema and no parameter explanation, an agent is left to infer how the limit affects results and exactly what the returned structure looks like. It is adequate but has clear gaps.

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%, and the description does not explain the meaning or interplay of the domain and limit parameters. The domain parameter is implied by the domain-focused output, but limit is never mentioned, so the description adds no value beyond the raw input schema.

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 explicitly states the tool returns SSL certificates from Certificate Transparency logs, including issuer, expiry, and a deduped subdomain list. This clearly differentiates it from sibling DNS tools by naming its data source and unique subdomain extraction behavior.

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?

It openly lists concrete use cases: shadow-IT detection, sales-intel hostname discovery, and phishing-cert monitoring. It provides clear context for when the tool is valuable, though it does not explicitly say when not to use it or name alternative tools.

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