get_latest_cert

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

With no annotations, the description carries the full burden. It discloses the return format including the null sentinel for cold domains and explains the enrichment behavior. This is adequate for a read-only tool, but could mention any caching or data freshness details.

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 efficient sentences. First sentence states core purpose with edge case; second explains optional parameter. No wasted words, front-loaded.

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 tool is simple (2 params, 1 required) and has an output schema described externally. The description covers core behavior, edge case, and optional enrichment. Missing domain format specification but otherwise complete.

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?

Input schema has 0% coverage (no parameter descriptions). The description adds meaning for include_enrichment by detailing what enrichment includes, but leaves domain parameter underdefined (no format or validation hints). Some compensation but not full.

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 clearly states the tool retrieves the most recently issued certificate for a domain, including the edge case of null with a backfill sentinel for cold domains. This specific verb+resource combination distinguishes it from siblings like get_certificate (specific certificate) and get_domain_certificates (all certificates).

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 provides guidance on when to use include_enrichment=true, explaining the additional context it provides (RDAP, DNS, ASN/hosting). However, it does not explicitly state when to use this tool versus siblings, though the sibling names and tool name offer implicit guidance.

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