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 full burden for behavioral disclosure. 'Update' implies a mutation, but the description doesn't specify required permissions, whether changes are reversible, potential side effects (e.g., DNS propagation delays), or error conditions. It lacks critical context for a write operation in a DNS management system.

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 extremely concise—a single three-word phrase—and front-loaded with the core action. There's no wasted verbiage. However, this brevity comes at the cost of completeness, as it omits necessary context for effective tool use.

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 complexity of updating DNS zone settings (a mutation with 6 parameters, no output schema, and no annotations), the description is insufficient. It doesn't cover behavioral aspects, usage context, or output expectations. For a tool that modifies critical infrastructure, more guidance is needed to ensure correct and safe invocation.

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 parameters are well-documented in the schema itself. The description adds no additional meaning about parameters beyond implying general 'settings' updates. It doesn't explain relationships between parameters (e.g., that 'nameserver1' and 'nameserver2' are only relevant if 'customNameserversEnabled' is true) or provide usage examples.

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 'Update DNS zone settings' clearly states the verb ('update') and resource ('DNS zone settings'), making the purpose understandable. However, it's somewhat vague about what specific settings can be updated, and while it distinguishes from obvious siblings like 'dns_create_zone' or 'dns_delete_zone', it doesn't explicitly differentiate from 'dns_update_record' which also modifies DNS data.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing DNS zone), exclusions, or compare it to related tools like 'dns_update_record' (for individual records) or 'dns_get_zone' (for viewing settings). The agent must infer usage from the tool name and schema alone.

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