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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful context about what the payload contains (valid vs expired status, issuer, validity window), but nothing about failure modes, missing-cert behavior, or external lookups implied by openWorldHint.

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 sentences, zero filler, and the core behavior is front-loaded ahead of the parameter clarification. Every clause carries information the agent needs.

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?

An output schema exists, so the description is not obliged to enumerate return fields, yet it does so anyway for scanning value. With one required parameter, annotations covering safety, and the scan_id source explained, an agent has everything needed to invoke it; only usage routing against sibling cert tools is absent.

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 coverage is 0%, so the schema only offers 'Scan Id' as a string title; the description compensates by defining it as the UUID of a ScanMalware scan, which is meaningfully more than the schema provides. With only one parameter, this is close to fully specified, though it does not describe format expectations or error behavior for a bad UUID.

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?

Names a specific verb and resource ('Get the TLS certificate the scanned site presented') and enumerates the returned fields (subject, issuer, validity dates, validity status), which makes it distinguishable from get_tls_asn1 and get_ct_certificates. It stops short of explicitly contrasting itself with those siblings, so it falls one notch below a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for adjacent cert-related needs (e.g. get_tls_asn1, get_ct_certificates). The only context given is that scan_id comes from a ScanMalware scan, which is input semantics rather than usage routing.

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