bunny_list_storage_zones

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

Annotations already convey read-only, idempotent, non-destructive behavior, so the description doesn't need to repeat those. The description adds account-level scope and domain context about storage zones being containers with regions/replication that can act as origins. It could mention pagination or deleted-zone handling, but annotations lower the burden.

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 concise sentences with no filler. The action is front-loaded, and the two explanatory sentences about storage zones add useful context without bloating the description.

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 and schema together cover the tool's purpose, optional parameters, and safety profile. It lacks an explicit statement of return shape or how pagination interacts with 'all', but for a simple read-only list tool with no output schema, this is still adequate for an 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 schema covers all three parameters with descriptions and defaults, so the description need not elaborate. It adds no special meaning beyond what the parameter descriptions already provide, but it also doesn't conflict.

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 states a specific action ('List'), a clear resource ('all Edge Storage zones'), and the scope ('in the account'). It is easy to distinguish from single-zone retrieval tools like bunny_get_storage_zone because 'all' signals a collection operation.

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 implies this tool is for enumerating storage zones, and the note about zones serving as origins gives a use case. However, it never explicitly says when to prefer this over bunny_get_storage_zone or how pagination behavior should inform usage.

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