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

Beyond the `readOnlyHint`, the description reveals critical behavioral traits: the specific data sources consulted (CISA KEV, NVD, GitHub advisories, etc.) and the complex, tiered logic of the default sorting algorithm. This is behavioral context not present in the structured annotations.

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 highly effective. It packs a lot of information into two sentences—defining the scope and then detailing the default execution logic—without becoming overly verbose or repetitive.

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 description provides all the necessary context for an agent to understand the scope of its search, its limitations (it searches specific public repositories), its default logic, and even guarantees the inclusion of source URLs in results. This is highly complete for a search 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?

Given the low schema description coverage (43%), the description is vital. It clarifies that the `query` can handle CVE IDs, products, or event names, and most importantly, it explains the entire logic behind the `sort` parameter's default 'urgent' setting.

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 specifies the resource ('KEVWire corpus') and the exact actions ('Search the KEVWire corpus'). It explicitly mentions the types of data searched (CVE, advisories, breaches), making the purpose crystal clear and distinct from listing or retrieval 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?

It provides clear guidance on default behavior, stating that the default sort order prioritizes urgency (last 30 days, exploitation, CVSS 9+, breaches). This provides a strong context for how the tool behaves without user intervention.

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