CDN traffic/requests report

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the '[READ]' tag merely repeats the read-only annotation. The 'ar-prometheus-exporter' note hints at the data source but adds nothing about return shape, aggregation, or freshness. Little value beyond structured 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?

A single front-loaded line with no padding or redundancy. It is efficient, though the terseness reflects under-specification rather than deliberate economy.

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 report tool sitting in a dense family of near-identical CDN report siblings with no output schema, the description is inadequate: it neither disambiguates nor describes the returned data. An agent would struggle to pick it over adjacent report tools.

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 coverage is only 50%: 'period' is fully documented by the schema (enum + default + description) while 'domain' has no description. The '?period=' hint adds nothing beyond the schema enum, and the undocumented domain param is left unexplained.

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 conveys a read of a CDN traffic/requests report via a specific endpoint, so the verb+resource is inferable, but it is largely a raw endpoint dump rather than a stated purpose. It gives no differentiation from the many sibling report tools (get_cdn_visitors_report, get_cdn_geo_report, get_cdn_response_time_report, get_cdn_status_report).

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?

There is no indication of when to use this report versus the other CDN report siblings. No prerequisites, no context, no alternatives are named.

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