run_sigma_lineage

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

No annotations are provided, so the description must carry the full burden. It mentions running a hunt and lineage tracing, and returning results, but does not disclose side effects like file writes to output_dir, required permissions, or whether it modifies input data. The read-only or destructive nature is unclear.

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, which is concise but at the cost of clarity. It front-loads the core action but omits necessary details. It is not verbose, but brevity reduces utility.

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 6 parameters (4 required) and a complex workflow (hunt + lineage), the description is severely incomplete. It does not explain prerequisites, output format (despite having an output schema), or typical use cases. The description fails to provide a minimal operational context for the agent.

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?

With 0% schema description coverage, the description adds no meaning to parameters. It mentions evtx_path, sigma_rules_path, mapping_path, and output_dir implicitly, but does not define them, their formats, or relationships. Parameters 'levels' and 'skip_hunt' are completely ignored, offering no guidance on usage.

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 runs a Sigma hunt with lineage tracing, returning paths/summary. It implies a combination of hunt and lineage steps, distinguishing it from 'run_sigma' sibling which likely does only the hunt. However, it could be more explicit about what 'process_lineage paths/summary' entails.

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?

No guidance on when to use this tool versus siblings. Sibling 'run_sigma' suggests a simpler hunt-only option, but the description does not explain the trade-offs (e.g., when lineage is needed). No when-not or alternative context provided.

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