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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real value by enumerating what the payload contains — severity, patch status, fixed versions, timeline, sources — which matters because no output schema exists. It does not say what happens on an unknown id (error vs empty), which keeps it from a 5.

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?

A single dense sentence with zero filler; the accepted identifier forms come first and the returned fields follow. The noun-phrase framing ("The incident covering…") is slightly awkward as an opening but costs no clarity.

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?

For a one-parameter, read-only lookup with no output schema, the description covers both input forms and the shape of the response. The remaining gap is failure behavior for an unrecognized id and the boundary with sibling tools.

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% and the single `id` parameter already documents accepted formats (CVE-2026-12345, GHSA-xxxx, HTTP2Shell). The description restates the same accepted identifiers without adding syntax, normalization, or resolution behavior, so it neither compensates nor detracts — baseline 3.

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 makes clear the tool returns an incident record (summary, severity, patch status, fixed versions, timeline, sources) for a CVE/GHSA id or named bug, which is specific and materially clearer than the name alone. It lacks an explicit verb and never names or contrasts with siblings like check_repo or check_lockfile, so it falls short of a 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 statement of when to reach for this tool versus the sibling tools, and no preconditions or exclusions. An agent must infer the usage context purely from the tool name and the listed return fields.

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