Chainsaw: summarise a result

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the "without paging" aggregation trait, but says nothing beyond the schema about cost, limits, or return shape for an aggregation tool with no output 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?

Two short sentences, zero filler, and the core capability (aggregate without paging) is front-loaded before the workflow sentence. Nothing repeats the title or annotations.

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?

No output schema exists, but the description names what the default overview yields (rules, levels, hosts, channels, event IDs, hours), so an agent knows the shape of the aggregated response. It does not explain the grouped-mode return format, a minor gap.

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 100%, so handle, top, where and group_by are already documented, including the default overview contents and the where-matching inheritance from chainsaw_result_page. The description's mention of users/processes/IPs/logon IDs as pivot fields adds only marginal color over the schema's own examples. Baseline 3 applies.

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?

Specific verb+resource ("Aggregate a stored result") with an explicit scope qualifier ("without paging through it") that immediately separates it from the paging siblings like chainsaw_result_page. It also differentiates the two modes it offers: default overview versus group-by pivots.

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?

Gives a concrete workflow: use the default overview to understand a hunt, then group by event fields to build pivots for chainsaw_search. That is clear when-to-use guidance tied to a named sibling. It stops short of saying when NOT to use it (e.g., when you need raw events, use chainsaw_result_events).

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