Generate and transform native SCF input waveforms

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

Annotations already declare destructive=true, idempotent=false, and closed-world; the description adds concrete safety/constraint context beyond that: exact 0.1ns grid, a 200000-event bound, and preservation of waveforms outside edited half-open ranges and opaque records. It also notes a fresh original simulation computes outputs, and it does not contradict annotations.

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?

Three compact sentences, with capabilities front-loaded and no filler. The first sentence is a list fragment and 'bounded200000' is a minor formatting slip, but the description stays appropriately short for a tool with rich schema documentation.

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 destructive editor with nested operations and no output schema, the description supplies key constraints—grid, event bound, preservation scope, simulation recompute—but omits when to use it versus siblings and does not explain operation composition or preview/confirm behavior. The schema covers parameters, but the description's guidance remains incomplete.

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%, so the schema already documents all six top-level params and nested operation fields; the description mainly echoes grid/half-open/MSB-first details that are also in the schema. It adds a few constraints (200000 total events, preservation semantics), but not enough to lift beyond the baseline for fully documented params.

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 the resource (native SCF waveforms) and enumerates specific operations—clock, repeat, counter, shift, invert, fill, copy—so the agent can tell it generates/transforms stimulus rather than inspecting it. It does not explicitly name a sibling tool or say 'edit,' so it stops short of the 5 threshold for sibling differentiation.

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 when-to-use guidance, prerequisites, or alternatives are given; the agent is left to infer that this is the mutation tool among many scf_* and stimulus_* siblings. It does not say when to choose it over scf_edit, scf_structure_edit, or stimulus_write.

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