bunny_get_dns_statistics

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

The readOnlyHint annotation already covers the safety profile, so the description does not need to restate that this is a read operation. It adds useful context about the returned statistics, but it does not disclose behavioral details such as date inclusivity, timezone handling, or any limits on the date range.

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 with no filler. It front-loads the action and resource, then adds the key output dimensions, making it easy to scan and understand quickly.

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 statistics tool with three clearly documented parameters and no output schema, this description is nearly complete. It explains what the caller gets back and clarifies the zone and date-range scope. A note about whether the date range is optional or how defaults behave would make it fully 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?

The input schema already documents all parameters: id is the DNS Zone ID, date_from and date_to have format and meaning. The description merely restates the date-range concept and does not add significant new meaning beyond what the schema provides, so the baseline 3 applies.

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 and resource: retrieve DNS query statistics for a zone over a date range. It also names the returned dimensions (total queries, queries by record type, response code distribution), which clearly differentiates it from sibling tools like bunny_get_dns_zone 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 gives clear usage context: it is for DNS query statistics scoped to a zone and a date range. It does not explicitly name alternatives or exclusions, but the zone and date-range scoping is sufficient for an agent to select this tool over account-level or storage-zone statistics tools.

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