Assess CVE applicability

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior: two evaluation gates (fix already present / not introduced, config mapping) and a guaranteed evidence chain on every verdict. It omits auth/permission needs, behavior when the CVE is unknown or the config mapping is absent, and any cost or latency characteristics.

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 with the core action front-loaded, followed by the evaluation gates and the output guarantee. The only friction is the unexplained shorthand '(R3)', which costs a little clarity for an agent with no key to the notation.

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 tool with no annotations and no output schema, the description covers the mechanism and one output property (evidence chain) but leaves the verdict shape, possible verdict values, and failure modes undefined. Adequate to call correctly, thin on what comes back.

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%, but the single parameter is a self-evident 'cveId' whose format is already pinned by the schema's regex pattern. The description says only 'a CVE', adding no syntax, sourcing, or format guidance beyond the schema, so it neither compensates nor misleads.

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 states a specific verb (cross-reference) and resource (a CVE) and scopes the operation to this system's version, config and modules, which separates it from a plain lookup like query_cve. It does not explicitly name a sibling tool to differentiate against, but the assessment semantics are unambiguous.

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?

Usage is only implied: the two-gate framing (version range, config mapping) tells the agent this is the 'does this CVE affect me' step, presumably after query_cve and before find_patches, but no when-to-use, when-not, or named alternative is given. Nothing is misleading, but nothing routes the agent either.

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