bunny_manage_pull_zone_hostnames

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

The description discloses that this is a mutating operation (add/remove), which aligns with readOnlyHint=false. It adds useful behavioral details beyond annotations: automatic SSL certificate provisioning and the required CNAME setup. No annotation contradiction is present.

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?

Three tight sentences with no filler. The main action is front-loaded, and the operational details (CNAME, SSL) follow naturally. Every sentence earns its place.

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?

For a simple tool with three required parameters and no output schema, the description covers the essential before/after behavior: what the action is, what follow-up step is needed, and a notable automatic side effect. It could mention removal-specific implications, but the low complexity and strong schema coverage make this a minor gap.

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 schema already documents id and action with 100% coverage, so the baseline is 3. The description adds value by giving a concrete hostname example and explaining the CNAME relationship, which helps an agent understand what hostname means in context even though the schema already labels the parameter.

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 specific verb pair, 'Add or remove', a concrete object, 'custom hostname', and the scope, 'on a CDN pull zone'. The example cdn.example.com makes the resource concrete, and this clearly distinguishes the tool from sibling pull-zone tools like bunny_update_pull_zone or bunny_delete_pull_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?

It gives practical context: after adding a hostname, point a CNAME record to the pull zone's b-cdn.net hostname, and notes that SSL is provisioned automatically. It does not explicitly name alternatives or state when not to use this tool, but the intended use case is clear.

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