Get vCDN statistics

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds valuable behavioral context by clarifying that date parameters are mandatory for most reports and providing an ISO date format example. It does not contradict annotations and goes beyond the schema by tying parameter requirements to each report type.

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 dense but efficient; each clause carries informative content. It front-loads the primary verb and resource, then lists reports in a structured sentence. It is longer than ideal, but every detail earns its place, covering all report types and requirements without redundancy.

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?

Given the tool's complexity (8 report types, 5 parameters, no output schema), the description covers parameter constraints and date formatting effectively. It does not describe the response structure or return values, but the report names are self-explanatory, and with annotations covering safety, the description is sufficiently complete for an AI agent to invoke 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?

Although the schema already documents each parameter, the description significantly enhances semantics by mapping specific parameters to each report type. For instance, it specifies that 'by_domains' requires resource_id and domains, and that 'bandwidth' is optional. This mapping is not evident from the schema alone and directly aids correct invocation.

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 clearly states the tool retrieves Video CDN statistics and enumerates eight specific report types (monthly_totals, timeseries, by_domains, etc.), each with distinct scopes. This specific verb+resource pairing and the detailed report list distinguish it from sibling tools like get_cdn_metrics or list_vcdn_domains.

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 practical context by specifying which parameters each report requires (e.g., 'monthly_totals' requires resource_id; 'by_domains' requires resource_id and domains) and notes that start_date/end_date are required for all reports except monthly_totals. It does not explicitly name alternatives, but the report-specific guidance serves as clear usage direction.

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