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

readOnlyHint=true already declares the safe-read profile, so the bar is lower; the description nonetheless adds real value by enumerating what the compact view contains (id, name, origin URL, enabled/suspended, hostnames, linked storage zone, bandwidth, charges) and what full=true expands. It does not mention pagination limits at the tool level, but the schema covers those.

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?

Front-loaded with the core action, followed by the one behaviorally important distinction (compact vs full) and the API endpoint. The inline field enumeration is slightly dense but each item earns its place by describing the default payload.

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 read-only list tool with no output schema, the description adequately conveys what comes back and how to widen it. Pagination and filtering semantics are fully covered by the schema, leaving no significant gap for an agent to call it correctly.

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 a 3 is the baseline, but the description goes beyond it by spelling out the difference between the compact and full response modes, which gives the boolean `full` concrete meaning. The page/search/per_page parameters are left entirely to 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?

States a specific verb (List) and resource (CDN pull zones on the account), plus the underlying API endpoint (GET /pullzone). This cleanly distinguishes it from bunny_get_pull_zone (single zone) and the other bunny_list_* siblings for storage zones and DNS zones.

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?

Explains the default compact response and when to set full=true, which is useful operational context, but never names alternatives or states when to prefer this over bunny_get_pull_zone or bunny_get_billing. Usage is implied rather than explicit.

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