Bunny.net MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a DNS zone' implies a destructive, irreversible mutation, but it fails to specify permissions required, whether it's synchronous/asynchronous, error conditions (e.g., if the zone doesn't exist), or side effects (e.g., impact on associated DNS records). This is inadequate for a destructive tool with zero annotation coverage.

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, direct sentence with zero wasted words—'Delete a DNS zone' is front-loaded and efficiently conveys the core action. It avoids redundancy or unnecessary elaboration, making it easy 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?

Given this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as what deletion entails (e.g., irreversible removal of all zone data), expected outcomes, error handling, or dependencies. For a tool that permanently modifies infrastructure, this minimal description poses risks for an AI agent.

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 100% description coverage, with 'dnsZoneId' documented as 'DNS zone ID'. The description adds no additional parameter semantics beyond what's in the schema. With high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter information.

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 ('Delete') and resource ('a DNS zone'), making the purpose immediately understandable. It distinguishes from siblings like 'dns_delete_record' (which deletes individual records) and 'dns_disable_dnssec' (which modifies zone security settings) by focusing on the entire zone. However, it doesn't specify what a DNS zone deletion entails beyond the basic action.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., ensuring the zone exists via 'dns_get_zone' or 'dns_list_zones'), consequences (e.g., all records are removed), or when not to use it (e.g., if the zone is critical). The description is purely functional without contextual advice.

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