start_etw_trace

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

With no annotations, the description carries full burden. It discloses elevation requirement, which is a key behavioral trait. However, it does not describe the trace lifecycle (e.g., runs until stopped, creates ETL file) or system impact.

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?

Single sentence with no wasted words. Information is front-loaded: purpose and elevation first, then provider format. Highly concise.

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?

Given moderate complexity (3 params, no output schema, no annotations), the description adequately covers purpose, elevation, and provider format. However, it lacks completeness on trace output (e.g., .etl files created in output_dir) and the need to stop the trace with stop_etw_trace.

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 67%. The description adds meaning for the 'providers' parameter by specifying format ('Microsoft-Windows-Kernel-* names or GUID strings'), which is not in the schema. It does not add to session_name or output_dir but partially compensates for missing schema 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 it starts a kernel ETW trace via logman and requires elevation. It specifies the resource and action, and distinguishes from siblings like stop_etw_trace and list_etw_providers.

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?

Elevation requirement is noted, but there is no explicit guidance on when to use this vs alternatives (e.g., stop_etw_trace, list_etw_providers). Usage context is clear but lacks exclusions.

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