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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), and the description adds substantial value beyond them by enumerating the returned facts: incident id, title, severity, whether exploited in the wild, publication date, verified fixed version and whether a fix procedure exists. The openWorldHint=false annotation is consistent with a lookup against the server's own incident data. It does not cover what happens on no match or how many results come back.

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?

Three tight sentences: what it takes, what it returns, and what the optional parameter modifies, in that order. The opening is a fragment ('Known security issues of one program...') but nothing is redundant and no sentence could be dropped without losing information.

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 no output schema, the description correctly spends its space enumerating the return fields and the meaning of the single optional parameter, which is what an agent needs to interpret results. Minor gaps remain around result cardinality and the empty-result case, but the essential contract is covered.

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 100%, so the baseline is 3, but the description goes further than the schema by explaining that os narrows fix availability to one system rather than merely being 'the user's operating system'. That is real added semantic meaning for the optional parameter.

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 names a concrete resource (known security issues) and the two accepted input kinds (a program/app/package name or a CVE id), with examples such as Chrome, Node.js and VS Code. It is unmistakably distinct from inventory or digest tools in substance, but it never explicitly contrasts itself with siblings like latest_incidents or get_fix_prompt, which keeps it at 4 rather than 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 stated when-to-use or when-not guidance: nothing says whether to reach for this versus latest_incidents for a feed or get_fix_prompt when remediation is the goal. The examples only clarify acceptable query values, not selection between tools.

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