Get CDN metrics

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

The annotations declare readOnlyHint=true and openWorldHint=true. The description adds behavioral detail beyond annotations by explaining the two time-selection modes, the ability to scope to the whole account or a single resource, and clarifying that 'responses' refers to HTTP codes. No contradiction with annotations.

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 two concise sentences that front-load the purpose and then provide essential usage details. Every sentence contributes valuable information with no redundancy or filler.

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?

Despite having no output schema and 9 parameters, the description covers the main scope, time-selection options, and metric types, which is sufficient for invoking the tool. It does not explain output structure, but the schema covers parameter constraints (like scale limits), so the description adequately complements the structured information.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the mutually exclusive time-selection modes (period+date vs from+to) and clarifying the 'responses' metric type as HTTP codes, which is not obvious from the schema alone.

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 it retrieves Anycast CDN metrics for the whole account or a single resource, giving a specific verb, resource, and scope. Listing metric types further distinguishes it from sibling tools like get_prometheus_metrics and get_bucket_metrics.

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 provides clear usage context by explaining the two time-range selection methods (period+date or from+to) and enumerating metric types. It does not explicitly contrast with alternatives, but it gives enough context for when to use this tool over others.

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