cf_query_bot_events_grouped

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

Given no annotations, the description fully discloses internal behavior: queries firewallEventsAdaptiveGroups with a pre-applied 'botManagement' filter, explains why (no standalone bot dataset), and specifies allowed group_by dimensions. This is transparent beyond schema.

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 concise at about 6 sentences, well-structured with the main purpose first followed by technical details and cross-references. No redundant information.

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?

Provides important context about internal data source and dataset limitations, but lacks practical details on parameter usage (e.g., date formats, filter structure). An output schema exists, so return values are less needed, but still, completeness is moderate.

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 0%, but the description only adds meaning for 'group_by' (allowed dimensions are firewall set) and indirectly mentions limit and cursor are pagination parameters. However, it fails to clarify formats for 'since', 'until', or usage of 'filters', 'zone_id', etc. The description does not sufficiently compensate for lack of 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 tool groups bot-management events by dimensions over a time window. It distinguishes itself from sibling tools like cf_query_http_requests_grouped by specifying that bot score dimensions are not included, making its purpose very specific.

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?

Provides explicit guidance on when to use this tool vs. the alternative cf_query_http_requests_grouped for bot score distribution. Also explains that the tool internally queries a filtered dataset, setting clear expectations.

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