bunny_create_storage_zone

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

Annotations already indicate this is a mutating (not read-only) operation and not marked destructive. The description adds useful context about optional replication for geo-redundancy and the default primary region, but it does not disclose side effects like billing, propagation, or duplicate-name behavior.

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 three sentences with no filler. The primary action is front-loaded, and the region guidance is concise and directly actionable.

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?

The description plus schema fully cover the required name and optional region/replication parameters. With no output schema, the description could mention what the created zone returns, but for a create tool the main calling context is sufficiently complete.

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 the description does not need to document parameters. It does add some semantic value by explaining that replication regions are for geo-redundancy and stating the default region, but this mostly mirrors the schema's parameter descriptions.

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 'Create a new Edge Storage zone,' a specific verb and resource that cleanly distinguishes it from sibling tools like bunny_list_storage_zones and bunny_create_video_library. It also explains the purpose of the region parameters, so an agent immediately understands what this tool is for.

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 clearly implies this tool is for creating a new storage zone and gives guidance on region selection, but it does not explicitly contrast it with list/get storage zone tools or other create tools. However, the resource-specific wording and sibling names make the intended use unambiguous.

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