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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is partly covered. The description adds genuine behavioral context beyond that: data provenance (KEV / CISA-SSVC-active / high-EPSS ranking, 'grounded in exploitation data, not model guesses'), the output ordering principle (dig_rank), and the explicit 'never a payload' assurance.

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?

Front-loads the core action and output, then documents args compactly. The closing line ('Grounded in exploitation data, not model guesses; lays out facts... never a payload') is slightly redundant with the earlier ranking claims but reinforces the no-payload guarantee, so it mostly earns its place.

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?

There is no output schema, yet the description adequately characterizes the return shape: ranked CVEs with source priorities, recurring_loci bug classes, and component dig_rank ordering. An agent has enough to know what it will get and how to call it, though pagination/limits and component-matching behavior are unstated.

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 does so well: technologies is explained with a concrete example list ('craftcms 4.4', 'nginx', 'keycloak'), and per_tech is defined as the count of top CVEs per component with its default of 4. Both parameters are given usable meaning that the schema lacks.

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 (turn/rank) and resource (a recon'd stack into a ranked dig-order), and precisely describes the composite output: per-component CVEs plus recurring_loci CWE classes. This differentiates it cleanly from siblings like search_vulns and enrich_cve, which act on individual CVEs rather than a whole stack.

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?

States the context ('authorized bug-hunting', post-recon stack, triage/where-to-look) and the framing intent clearly. It does not explicitly name when to prefer it over siblings like search_vulns or find_attack_approaches, so it stops short of a full when/when-not rubric.

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