winops_evtlog_export

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

Annotations indicate readOnlyHint=false, so the tool is a write operation, which is consistent with the description. It adds the note that the output is a .evtx file, but does not disclose potential side effects (e.g., file overwriting, required permissions, failure behavior). The return format is useful but does not go beyond what the output schema provides.

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 with a clear one-line purpose, a return format section, and an example. It is well-structured and front-loaded. The example is helpful but could be slightly more compact; still, every component earns its place.

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 is relatively simple with only two parameters and an output schema, so the description is mostly adequate. However, it lacks details on error conditions or permission requirements, and since annotations are sparse, a bit more context would enhance completeness.

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 describes both parameters. The description provides an example that clarifies 'output_path' format (e.g., D:\logs\system.evtx) and 'log_name' usage (e.g., 'System'), but does not add substantial additional meaning beyond the schema.

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 exports a Windows Event Log channel to an .evtx file, with a specific verb and resource. It is distinct from siblings like winops_evtlog_query and winops_evtlog_clear, though it does not explicitly contrast with them.

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 provides a basic example and implies the tool is for exporting logs, but does not explicitly state when to use it versus alternatives like querying logs (winops_evtlog_query). It lacks guidance on prerequisites (e.g., permissions, existence of the log channel) or exclusions.

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