security_cve_audit

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

The annotations already declare read-only, non-destructive, open-world behavior, and the description adds that the tool draws on OSV.dev and FIRST.org EPSS exploit scoring. It does not disclose rate limits, authentication needs, or the shape of the advisory output, so it adds useful but limited behavioral context beyond the annotations.

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 front-loaded sentence with no wasted wording. It states the action, target, and external sources compactly.

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-only audit tool with a fully described schema and helpful annotations, the description is largely complete. It identifies the data sources and auditing purpose, though it could be slightly stronger by clarifying how the output relates to CVE advisories and EPSS scores.

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 package, version, and ecosystem parameters are already well documented in the schema. The description does not add syntax, defaults, or meaning beyond what the schema provides, which is the expected baseline when schema coverage is high.

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 and resource: auditing package vulnerabilities and CVE advisories. It also names the data sources, OSV.dev and FIRST.org EPSS, but it does not explicitly distinguish this tool from siblings such as epss_exploit_score or package_health_pulse.

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 implied by the audit-oriented wording, but the description provides no explicit when-to-use guidance, prerequisites, or comparison to alternative security tools in the sibling list. An agent can infer its purpose but is not routed clearly between this and epss_exploit_score.

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