export_audit_log

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that — PII scrubbing, tamper-evidence, and file-vs-stream output — but says nothing about permissions, append-vs-overwrite behavior, or what the emitted event contains.

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?

Two tight sentences with the core capability front-loaded. The leading 'Zero-Trust Enterprise Compliance:' label is marketing framing that does not help an agent decide or invoke, but the rest is efficient.

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 six-optional-parameter export tool with no output schema, the description covers formats, PII handling, and the file/stream destination choice. It leaves the shape of the returned log event and any permission requirements unstated, which is a modest gap given annotations already carry the safety profile.

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 100%, so every parameter is already documented, including the format enum and destination_file. The description's format list largely restates the schema, and it adds no syntax or constraint detail beyond what the schema provides, so the baseline 3 applies.

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 names a specific verb ('Exports') and resource ('immutable, tamper-evident audit log') and enumerates the output formats (CEF/ArcSight, RFC 5424 Syslog, JSONL, JSON). It is clearly distinguishable from siblings like generate_compliance_report or audit_context, though it never explicitly contrasts itself 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?

Usage is only implied: the SIEM/compliance framing suggests when an agent would want this, and 'can write directly to a local log file or stream' hints at the two output modes. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling tools.

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