bunny_get_storage_zone_statistics

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

Annotations already declare the operation read-only, idempotent, and non-destructive, so the description does not need to repeat that. It adds meaningful behavioral context by specifying the date-range input and the metrics returned, which goes beyond the structured annotation data.

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 a single, well-structured sentence that leads with the action and resource, then immediately lists the returned metrics. No filler or redundant phrasing is present.

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 read-only statistics tool with only three parameters, the description adequately covers the purpose and returned data. There is no output schema, so listing the specific metrics is valuable; however, it does not explain behavior when date_from/date_to are omitted, which is 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?

Schema description coverage is 100%, with every parameter already described meaningfully (Storage Zone ID, end date, start date). The description adds the high-level context of 'usage statistics over a date range' but does not provide additional parameter-level detail beyond the schema.

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 uses a specific verb ('Retrieve') with a clear resource ('storage zone usage statistics') and enumerates exactly what metrics are returned: storage space used, file count, and bandwidth consumed. This clearly distinguishes it from sibling tools like bunny_get_dns_statistics or bunny_get_statistics.

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 makes the tool's scope explicit: it is for storage zone usage statistics over a date range. It does not explicitly name alternatives or exclusions, but the resource-specific wording provides clear context for when an agent should select this tool among the many siblings.

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