Chainsaw: dump records

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

Annotations only flag readOnlyHint=false and non-idempotent without explaining why; the description fills that gap by disclosing that output is materialized under a result handle and paginated. This explains the side effect that makes the tool not read-only. It does not detail persistence lifetime or cleanup, so 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?

Two tight sentences with the core action front-loaded and the usage condition immediately following. No filler; every clause carries 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?

With no output schema, the description still conveys the return model (JSON records under a result handle, paged). Parameters are fully covered by the schema. It leaves the exact paging tool and handle lifecycle implicit, keeping it from a 5.

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 schema already documents all six parameters in detail (fields, preview, extension, skip_errors, load_unknown). The description adds no parameter-level meaning beyond generic paging guidance, matching the baseline 3 for schema-driven tools.

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?

States a specific verb (convert/dump to JSON) and resource (every record in the evidence), and frames it against the hunt/search workflow. It distinguishes itself contextually as a follow-up step, though it does not explicitly name the sibling tools it is not (e.g. chainsaw_hunt, chainsaw_analyse_evtx).

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 clear when-to-use condition: after a hunt or search has narrowed scope to one or two files and you need the complete record stream. It also points at the follow-up action (page through the handle). No explicit exclusions or named alternative tools, so it stops short of a 5.

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