zins_get_web_traffic_by_location

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

Annotations already declare readOnlyHint=true, and the description reinforces that with 'Read-only analytics.' It adds behavioral details: each row is a location with totals, include_trend adds time-series, and window constraints. This provides useful context beyond the 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 sentences plus a brief note, every sentence adds value, and it is front-loaded with the core purpose. No extraneous content.

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 lack of an output schema, the description partially explains the result structure (location rows with totals and optional trend). However, it does not cover all 9 parameters or the full response format, leaving some ambiguity for a complex tool.

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 11%, so the description must compensate. It adds meaning for 'include_trend' and the time-window (start/end_days_ago) by explaining their impact. However, many parameters (limit, traffic_unit, trend_interval) remain undocumented, leaving gaps.

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 'Get web traffic aggregated per location', which is a specific verb+resource. The name and description distinguish it from siblings like 'zins_get_web_traffic_no_grouping' by explicitly mentioning per-location aggregation.

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 indicates it is read-only analytics and provides parameter guidance (include_trend, 7-14 day window). However, it does not explicitly state when to use this tool vs alternatives like the non-grouped version.

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