CDN geo traffic map report

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the '[READ]' tag merely echoes readOnlyHint rather than adding new behavioral context. There is no disclosure of return shape, pagination, aggregation granularity, or auth/rate-limit considerations for this report endpoint.

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?

It is a single compact line with no wasted words and front-loads the [READ] marker, but its brevity stems from under-specification rather than efficiency. Every word is 'used' but little useful information is conveyed.

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 with no output schema, the description should describe what the report returns (geo traffic distribution over a period). Instead it gives only the HTTP route, leaving the agent unable to know what data or aggregation to expect.

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 only 50%: 'period' is documented in the schema (including the METRICS_PERIOD note), but 'domain' carries only a pattern with no description. The description's endpoint string mentions {domain} and ?period= but adds no semantic meaning (e.g., what a geo map aggregation returns per period) beyond 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?

The description is essentially a raw endpoint reference ('GET /domains/{domain}/reports/traffics/map?period='), restating technical routing rather than stating in plain language what the tool produces. Only the name/title ('CDN geo traffic map report') convey the geo/map scope, and the description does not differentiate it from siblings like get_cdn_traffic_report, get_cdn_visitors_report, or get_cdn_response_time_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?

No when-to-use, when-not, or alternative guidance is given. With several sibling CDN report tools (traffic, visitors, response-time, status), the description offers no signal about when the geo/map report is the right choice versus those.

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