bunny_manage_dns_record

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

Annotations already signal readOnlyHint=false and destructiveHint=true, and the description's 'delete' operation aligns with that. It adds useful behavioral detail by requiring a record object for add/update and listing record types, but it does not disclose side effects, whether update/delete require a record ID, or any irreversible consequences beyond what the annotation already implies.

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 two sentences with no padding. It leads with the core action, packs the type map into a compact reference, and closes with the object fields. Every word serves a purpose.

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?

It is adequate for add operations, given annotations cover destructive behavior, but it does not state how update/delete identify the target record or whether a separate record ID is needed. There is no output schema and no mention of return/response behavior, which is a meaningful gap for a mutation tool.

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 this is above baseline. The description adds real value by mapping numeric Type codes to human-readable record types, clarifying the Name field (subdomain or empty for root), specifying Ttl in seconds, and noting that Priority applies to MX/SRV. It does not fully explain when priority/weight/port are required or how update identifies an existing record.

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 opens with a clear verb-resource pair: Add, update, or delete a DNS record within a zone. It explicitly enumerates the record types and the fields needed for add/update, making its domain unmistakable. This differentiates it from sibling zone-level tools like bunny_create_dns_zone or bunny_get_stonzage_zone.

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: this tool manages DNS records inside a zone, implying use when the target is a record rather than a zone. It does not explicitly name alternatives or give when-not-to-use conditions, so it stops short of a perfect 5.

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