cloudflare_web_analytics_stats

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

With no annotations, the description must disclose all behavioral traits. It states the tool is a query that returns data grouped by time, implying read-only operation. However, it does not mention authentication needs, rate limits, or any potential side effects. The 'grouped by time' detail adds some value, but overall transparency is minimal.

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, front-loaded sentence that communicates the core purpose and output succinctly. Every word adds value, 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?

Given the absence of an output schema, the description should fully explain the return format. It only lists the metrics and mentions grouping by time, but does not describe whether the result is a list, time-series array, or aggregated totals. Pagination behavior and limit effects are omitted. For a tool with 3 parameters and no output schema, this is insufficient.

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 description adds little beyond the schema. It mentions 'zone' context for zone_id and 'grouped by time' which hints at the time-based behavior of the since parameter, but this is not explicit about parameter usage. The description does not improve on the schema's already clear parameter descriptions.

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 verb 'Query' and the resource 'Web Analytics traffic stats for a zone', and specifies the returned metrics (page views, visits, bandwidth). This distinguishes it from sibling tools like cloudflare_web_analytics_list or cloudflare_web_analytics_get, which deal with analytics rule management rather than raw traffic stats.

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 no guidance on when to use this tool versus alternatives (e.g., cloudflare_worker_analytics or cloudflare_ddos_analytics). It does not mention prerequisites, such as requiring a zone_id, nor does it exclude scenarios where other tools might be more appropriate.

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