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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable context by naming data sources (CVE NVD, OpenCVE, GitHub Advisories) and disclosing potential timeout behavior with an async option. This goes beyond the annotations to inform the agent about response latency and external dependencies.

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 three sentences long, each serving a purpose: stating the core function, specifying input/output, and providing sources and async guidance. It is front-loaded with the main action and contains no redundant or filler wording.

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 annotations and an output schema present, the description covers the core use case and adds source/async context. However, it omits explanations for cloudProvider and includeDetails, and lacks guidance on choosing this tool over related vulnerability tools, making it adequate but not fully complete for a 4-parameter tool.

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 only 25% (only async has a description). The description explains the core cveId parameter with an example and mentions async to avoid timeouts, but it does not explain cloudProvider or includeDetails, leaving half of the parameters unspecified. This only partially compensates for the low schema coverage.

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 a specific verb ('assess') with a specific resource ('exploitability risk of CVEs') and distinguishes itself by mentioning EPSS scores and cloud asset exposure data. It also identifies the input (CVE ID) and output (exploitability likelihood, affected cloud services, threat intelligence context), making the tool's purpose unmistakable and distinct from generic CVE lookup tools.

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 implies a use case for CTOs prioritizing vulnerabilities but does not explicitly state when to use this tool versus siblings like cve_security_lookup or vuln_patch_priority_engine. It includes an operational hint about passing async:true to avoid timeout, but offers no exclusions or alternative tool references.

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