Katzilla MCP

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds valuable context beyond this: it specifies the data source (RIPE NCC), update frequency (daily), and return format (Katzilla envelope with quality scores and citation details), which helps the agent understand data freshness and auditability without contradicting 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 front-loaded with the core purpose, followed by source details and return format explanation in a single, efficient sentence. Every element (purpose, source, update frequency, return structure) serves a clear purpose without redundancy, making it highly concise and well-structured.

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 complexity (security data with daily updates), rich annotations (read-only, idempotent, open-world), and the presence of an output schema, the description is complete. It covers purpose, source, update frequency, and return format details, providing all necessary context for an agent to use the tool effectively without needing to explain parameters or basic behavioral traits already in annotations.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description compensates by explaining the return structure ('Returns the Katzilla envelope { data, quality, citation }') and what the quality scores represent ('freshness/uptime/confidence'), adding semantic value beyond the schema.

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 explicitly states the tool's purpose: 'Get the current list of RIPE Routing Information Service (RIS) BGP peers and their status.' It specifies the verb ('Get'), resource ('list of RIPE RIS BGP peers and their status'), and distinguishes it from siblings by focusing on security-related BGP data, unlike other tools in categories like agriculture, consumer, or entertainment.

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: 'Source: RIPE NCC (Open Data), updates daily.' This indicates when the data is relevant (daily updates) and its open-source nature. However, it does not explicitly state when not to use this tool or name alternatives among siblings, such as other security tools like 'security__cisa-kev' or 'security__nvd'.

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