Katzilla MCP

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds valuable context beyond this: it specifies the source (CISA, Public Domain), update frequency (daily), and details about the return format (Katzilla envelope with quality scores and citation data including SHA-256 hash). This enriches the agent's understanding of data freshness, auditability, and structure, though it doesn't mention rate limits or authentication needs.

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 front-loaded with the core purpose in the first sentence, followed by essential details about the source, update frequency, and return format. Every sentence adds value without redundancy, making it efficient and well-structured for quick comprehension by an AI agent.

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's simplicity (no input parameters, rich annotations, and an output schema implied by the description of the Katzilla envelope), the description is complete. It covers purpose, source, update frequency, and return structure, which is sufficient for an agent to understand and invoke the tool correctly without needing additional explanation.

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 input schema has no parameters (0 parameters, 100% coverage), so there are no parameters to document. The description appropriately does not discuss parameters, focusing instead on output behavior. A baseline of 4 is applied as it compensates for the lack of parameters by detailing the return format, which is helpful for the agent.

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 tool's purpose: 'Retrieve the CISA Known Exploited Vulnerabilities (KEV) catalog. Returns the full list of actively exploited vulnerabilities.' It specifies the exact resource (CISA KEV catalog) and verb (retrieve), distinguishing it from sibling tools like security__nvd or security__ioda, which focus on different security data sources.

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 usage: it's for retrieving the full list of actively exploited vulnerabilities from CISA, updated daily. However, it does not explicitly state when not to use this tool or name specific alternatives among siblings (e.g., security__nvd for broader vulnerability data), which prevents a score of 5.

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