CVE MCP Server

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

With no annotations provided, the description carries full burden. It discloses what the tool returns (malware family, detection stats, file metadata) and mentions two external services. However, it doesn't cover rate limits, authentication needs, error conditions, or whether this is a read-only operation (though 'look up' implies non-destructive).

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 efficiently structured with a purpose statement followed by return values and parameter details. Every sentence adds value: the first explains what and where, the second what it returns, and the third provides critical parameter format guidance.

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?

Given the tool has an output schema (so return values don't need description), 1 parameter with 0% schema coverage, and no annotations, the description does well by explaining parameter formats and return types. It could improve by mentioning rate limits or authentication, but covers the core functionality adequately.

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 has 0% description coverage, so the description must compensate fully. It provides crucial semantic information: the parameter accepts MD5 (32 hex), SHA1 (40 hex), or SHA256 (64 hex) hash formats, which is essential for correct usage beyond the schema's basic string type.

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 clearly states the verb 'look up' and the resource 'file hash' against specific services (MalwareBazaar and VirusTotal). It distinguishes from siblings by focusing on hash-based malware intelligence rather than IP reputation, URL safety, CVE lookups, or other security functions in the sibling list.

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 provides clear context for when to use this tool (when you have a file hash and want malware intelligence). However, it doesn't explicitly state when NOT to use it or name specific alternatives among the siblings, though the sibling list shows distinct tools for different security queries.

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