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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that the payload is a raw ASN.1 structure, which hints at the output's low-level nature, but says nothing about size, parsing needs, or failure modes when no TLS cert exists.

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 action and scope come first, the parameter note second. No filler, no redundancy with the title.

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?

With an output schema present, return values need no explanation, and annotations cover the safety profile. The description adequately conveys what is fetched and which identifier is needed; only the routing against get_tls_details remains implicit.

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 carries the burden, and it does clarify that scan_id is the UUID of a ScanMalware scan, which is more than the schema's bare 'Scan Id' title provides. It stops short of detailing format constraints or invalid-ID behavior.

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: fetching the raw ASN.1 structure of a TLS certificate from a single scan. It is distinct from get_tls_details because it emphasizes the 'raw ASN.1' payload for 'detailed certificate inspection', though it never names that sibling explicitly.

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?

'For detailed certificate inspection' implies the use case, but there is no explicit when-not or named alternative (e.g., get_tls_details for summarized cert info). The agent must infer that this is the deep-dive option versus the summary tool.

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