Export Audit Trail

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

With no annotations provided, the description carries the full burden. It discloses that the export includes all entries with hash chain, timestamps, and actor information, which is useful. However, it does not mention side effects like creating files via output_path, potential large data handling, or performance implications, leaving some behavioral aspects opaque.

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 two sentences, immediately states the tool's action and purpose, and avoids redundancy. Every sentence adds value: the first defines the action and format, the second elaborates on content included in the export.

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 the tool has 3 optional parameters and no output schema, the description covers the core purpose, formats, and content. It could be enhanced by mentioning the file-writing behavior or return value, but the schema parameter ('Path to write the export file') partially covers that. The tool is relatively simple, and the description is mostly complete for a compliance export.

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?

The schema already covers 2 of 3 parameters with descriptions, and the description adds context that the export is 'complete' and includes hash chain, which indirectly relates to include_details. However, it does not clarify the format enum semantics beyond what the schema provides, and the output_path default is not explained in the description. Overall, it does not significantly exceed schema value.

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 the complete audit trail in JSON or CSV format for compliance and legal documentation. It uses a specific verb ('export'), names the resource ('audit trail'), and specifies formats, distinguishing it from sibling tools like cleanroom_audit_log (likely logs events) and cleanroom_audit_verify (likely verifies integrity).

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 implies usage for compliance records and legal documentation, but does not explicitly state when to use this over alternatives like cleanroom_audit_log or cleanroom_audit_verify, nor does it provide exclusions or prerequisites. It offers a clear purpose but lacks explicit 'when not to use' guidance.

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