Security Intel MCP

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

With no annotations, the description carries the behavioral burden and does disclose meaningful behavior: it accepts a raw package.json or a dependencies array, returns per-package findings plus a summary, and defaults the ecosystem to npm. It does not cover edge-case behavior like what happens if both inputs are supplied or if the manifest is invalid, but the core behavior is transparent.

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 short sentences cover purpose, input modes, return behavior, and default ecosystem without repetition. The most important purpose statement is front-loaded, and every sentence contributes meaningful 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?

The description gives a solid high-level picture but leaves gaps: there is no output schema, and the return value is only described as 'per-package findings and a summary' with no detail on structure, severities, or counts. It also does not address ambiguous inputs, such as supplying both manifest and dependencies, or how errors like an invalid package.json manifest are handled.

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 adds real value by clarifying that manifest and dependencies are alternative input modes rather than independent optional fields. It also contextualizes the ecosystem parameter by stating the npm default, which is not inferable from the raw schema alone.

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 opens with a specific verb and resource: 'Audit a whole dependency manifest for known vulnerabilities in one call.' This clearly states what the tool does and its batch-oriented scope, but it does not explicitly differentiate it from the sibling tools cve_lookup or package_vulnerabilities.

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?

The phrase 'in one call' and 'whole dependency manifest' imply this is for bulk manifest auditing, and the description explains how to provide input via manifest or dependencies. However, it never states when to prefer this tool over cve_lookup or package_vulnerabilities, nor does it mention any exclusions.

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

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

With no annotations, the description carries the disclosure burden. It usefully states the return payload and the data source (NVD/NIST), but it does not mention error behavior, rate limits, network dependence, or other operational traits. This is adequate for a simple lookup but not deeply transparent.

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 a single, tightly packed sentence that leads with the action and then lists the result components in a scannable sequence. There is no filler, redundancy, or irrelevant context.

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 simple one-parameter tool with no output schema, the description covers the input, the output fields, and the source. It does not explain what happens for invalid or nonexistent CVE IDs, but that is a minor gap given the simplicity of the operation and the availability of sibling tool context.

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?

The schema already fully documents the single parameter cve_id with an example, so the baseline is 3. The description only confirms that the ID is a CVE identifier, adding no extra format, validation, or relationship details beyond what the schema provides.

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 action ('Look up a CVE by ID') and enumerates the exact contents of the result: description, CVSS score & severity, vector, CWE weakness, publish date, and references. This clearly distinguishes the tool from the sibling tools audit_dependencies and package_vulnerabilities, which focus on broader scanning rather than single-CVE lookup.

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 context is implied: use this tool when you already have a CVE ID and want a compact summary. However, there is no explicit guidance about when to prefer this over the sibling tools, nor any mention of situations where it should not be used.

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

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

The description discloses useful behavioral context: the data source is OSV, version filtering is optional, and only the listed ecosystems are supported. Since there are no annotations, the description carries the transparency burden, but it omits details such as the shape of the returned vulnerability list, empty-result behavior, and any access or rate-limit considerations.

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 two tight sentences with the core action front-loaded and the ecosystem list appended compactly. There is no filler, repetition, or unnecessary detail, making it easy for an agent to parse quickly.

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 simple three-parameter read tool, the description is mostly sufficient to invoke the tool correctly. However, there is no output schema and the description does not explain what fields the vulnerability results contain, nor does it route the agent away from sibling tools when the context is a dependency audit or a CVE lookup.

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 100%, so the schema already documents name, version, and ecosystem. The description adds a succinct restatement of the optional version and supported ecosystems, but it does not add significant meaning beyond what the input schema already provides.

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 uses a specific verb, 'List', and identifies a concrete resource: known vulnerabilities for a software package, optionally filtered by version, via OSV. It is distinct from the sibling tools because it is scoped to a package/ecosystem lookup, but it does not explicitly compare itself with audit_dependencies or cve_lookup.

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?

The description implies the tool's use case: call it when you need OSV vulnerability data for a named package in a supported ecosystem. However, it gives no explicit guidance about when to prefer the sibling tools instead, such as using cve_lookup for CVE IDs or audit_dependencies for dependency-tree auditing.

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