analyze_forensic_artifact

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

No annotations present, so description carries full burden. It only says 'analyze' without disclosing what the analysis produces (e.g., indicators, confidence scores), side effects, or any operational constraints. Behavioral transparency is minimal.

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, front-loaded with action and resource, efficiently conveys core purpose with no wasted words. The dash-separated list is clear and scannable.

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?

For a complex tool with 5 parameters, no output schema, and no annotations, the description lacks crucial details: what the analysis returns, how to interpret results, or any use-case constraints. It covers only basic purpose.

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% with parameter descriptions. The description adds value by mapping mode values to artifact types (e.g., 'event_log' corresponds to 'Windows Event Logs'), providing context beyond the schema's enum list.

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?

Description clearly states specific verb 'Analyze' and resource 'forensic artifacts for LOL technique indicators', listing explicit artifact types (Windows Event Logs, Process Monitor, EDR alerts, network captures). This distinctively separates it from sibling tools like analyze_binary or find_discovery.

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?

Description implies usage when forensic artifacts are available but provides no explicit guidance on when to use this tool vs alternatives (e.g., analyze_binary for binaries). No when-not-to-use or prerequisite conditions are mentioned.

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