stop_etw_trace

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the tool stops the trace, processes data via tracerpt, and returns a preview. The elevation requirement is also mentioned. However, it does not detail side effects such as session deletion or file cleanup.

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 a single sentence that conveys all necessary information concisely, with no wasted words. It is front-loaded with the primary action.

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?

The tool has 3 parameters, no output schema, and no annotations. The description covers the core action but lacks details on return value format, required permissions beyond elevation, or error conditions. It is adequate but leaves some gaps for an agent to fully understand the tool's behavior.

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?

The schema description coverage is only 33%, with only process_filter having a description. The tool description adds no additional meaning to the parameters; session_name and output_dir are left unexplained beyond their names. For a low-coverage schema, the description fails to compensate.

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 verb 'Stop' and the resource 'ETW trace', and further explains that it runs tracerpt to CSV and summary and returns a parsed preview, leaving no ambiguity about the tool's function. It is distinguishable from sibling tools like start_etw_trace.

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 mentions 'requires elevation', providing a clear prerequisite for usage. It implies that the tool should be used after starting a trace, but does not explicitly state when not to use it or compare with alternatives, which would have earned a higher score.

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