Export Waveform Spice

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, and the description's 'Write' aligns with that. However it adds no behavioral context beyond the annotations: it does not say where output goes, whether output_path must exist, or what happens on repeat calls.

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?

A single short sentence, but it is under-specified rather than concise. The brevity comes at the cost of essential information an agent needs, so it does not earn its place as a complete definition.

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 4-parameter export tool with no output schema and only 25% schema coverage, this one-liner is inadequate. It omits output destination, file format details, and parameter meaning, leaving the agent unable to invoke it confidently.

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 only 25% (workspace_root alone is documented), so the description must compensate for signal, raw_path, and output_path — and it does not. The vague reference to 'one real trace' hints at signal/raw_path semantics but conveys no format, selection, or destination meaning.

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?

States a specific verb ('Write') and a resource ('a PWL statement for one real trace'), but 'PWL' is unexplained jargon and the description never says it writes to a file or where. It also fails to distinguish this from siblings like export_waveform_ascii, export_waveform_csv, or export_derived_raw, all of which also export waveform data.

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 phrase 'for one real trace' gives a faint scope hint, but there is no when-to-use guidance, no prerequisites, and no named alternative among the many export_* siblings. An agent has no basis for choosing this over export_waveform_ascii/csv.

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