zins_get_web_traffic_no_grouping

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds genuine behavioral context: the fact that results are optionally filtered by 'DLP engine or action (ALLOW/BLOCK)', can include an overall time-series `trend`, and are constrained to a 7- or 14-day historical window. This exceeds simply restating the annotations, though it doesn't describe response shape or error behavior, so it's not a 5.

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?

Three crisp sentences: (1) verb+resource+differentiator, (2) behavior with optional filters/trend, (3) critical window constraint. Every word earns its place; no filler, well front-loaded with purpose.

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 an 11-parameter, no-output-schema tool, the description covers the essential decision points: what it returns (overall traffic), how to filter it, the trend option, and the fixed window requirement. The main gap is that parameters like `traffic_unit`, `trend_interval`, and `limit` are left to the agent's inference. That said, the tool is part of a large sibling family and the description does enough to let an agent choose and invoke it correctly in most cases.

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?

With only 9% schema coverage, the description carries important semantic weight. It explicitly names filters (`action_filter`, `dlp_engine_filter`) with their ALLOW/BLOCK semantics, references `include_trend`, and constrains the window implicitly via the required 7-14 day interval (which maps to `start_days_ago`/`end_days_ago`). It could have further documented `traffic_unit`, `trend_interval`, or `limit`, but it does meaningfully reduce ambiguity for the core options.

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 gets 'overall web traffic volume with no grouping' — a specific verb, resource, and scope. It differentiates from siblings like `zins_get_web_traffic_by_location` by emphasizing 'no grouping' and by describing the ungrouped/aggregate return. The name and description together leave no ambiguity about what this tool does.

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 a concrete usage constraint: 'Window must be a 7- or 14-day historical interval,' which disambiguates valid parameter ranges. However, it never explicitly states when to use this tool versus grouped alternatives like the by-location variants, nor does it mention the no-grouping vs grouping decision beyond the tool name. The guidance is implied rather than stated.

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