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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally; the description adds genuinely non-obvious behavioral context by disclosing that storage passwords are redacted and enumerating exactly which attributes come back. It does not mention auth/permission requirements or error behavior, keeping it short of a 5.

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?

Two compact sentences, zero filler: the returned-field list is front-loaded, the redaction caveat follows, and the API mapping is last. Every clause conveys information an agent would otherwise have to discover by calling the tool.

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?

With no output schema, the description compensates by enumerating the fields the call returns and flagging the redaction of passwords. For a one-parameter, read-only lookup with full schema documentation and matching annotations, nothing needed to invoke it correctly is missing.

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 a single documented required parameter (storage_zone_id), so the schema already carries the meaning. The description adds nothing about the parameter beyond the endpoint template's {id} placeholder, which is the expected baseline when the schema does the heavy lifting.

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+resource ("Fetch one edge storage zone") and immediately enumerates the fields returned (hostname, region, replication, storage used, files stored, 404 handling, connected pull zones). The word "one" plus the ID-based endpoint implicitly separates it from bunny_list_storage_zones and from the statistics sibling, so an agent can route correctly without opening a schema.

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?

Usage is implied rather than stated: "Fetch one" and the endpoint template GET /storagezone/{id} make clear this is the single-entity lookup, but the description never names alternatives (list_storage_zones, get_storage_zone_statistics) or states when not to use it. Adequate for a simple read, but the when-to-use-vs-siblings guidance is left to inference.

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