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

Beyond the read-only annotations, the description discloses the returned data fields, summarization behavior, source fallback from certspotter to crt.sh, throttling behavior, and the slower nature of expired-certificate searches. This adds substantial operational context.

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 front-loaded with the resource and scope, then moves through return fields, summary behavior, and source selection. It is dense but mostly efficient, though the first sentence is long and packs many details together.

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 tool without an output schema, the description explains the key returned certificate attributes and summary outputs. It also covers source fallback, expiry inclusion, and subdomain scope, leaving little ambiguity about what the call produces.

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 the schema already documents host, limit, source, include_expired, and include_subdomains. The description reinforces source and include_expired behavior but adds little parameter meaning beyond what the schema already provides.

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 states a specific verb and resource: retrieving certificate-transparency history for one hostname or domain. It clearly distinguishes the scoped host/domain lookup from broader sibling tools such as find_subdomains and summarize_attack_surface.

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 explains the main operating modes: default certspotter for unexpired certificates, include_expired for full crt.sh history, and include_subdomains for domain-wide lookup. It does not explicitly name alternatives or when not to use this tool, but the parameter-driven usage context is clear.

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