Prepare Transfer Function

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

Annotations already disclose the safety profile: readOnlyHint=false (a mutation) with destructiveHint=false, which is consistent with "insert". The description adds nothing beyond that — no statement about what gets modified (the schematic at schematic_path), whether insertion is idempotent, or whether a prior schematic must exist. With annotations present the bar is lower, but the description contributes essentially no behavioral context.

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?

It is a single short sentence with no padding, which is good, but the brevity is under-specification rather than concision. There is no front-loaded purpose statement or any structure to build on.

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 mutation tool with no output schema, no usage guidance, and 25% schema coverage, the definition is far too thin. Nothing tells the agent the required parameters' meaning, the preconditions, or how the inserted directive relates to the rest of the netlist.

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 25% (only workspace_root is documented), and three required parameters — output, source, schematic_path — are bare strings with no explanation. The description does not compensate at all: it says nothing about what output/source refer to (the transfer-function output node and input source) or the required schematic path. An agent cannot fill these correctly from the definition.

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?

"Insert a .tf directive" gives a concrete verb (insert) and a concrete artifact (.tf directive), which maps to the tool name prepare_transfer_function. However, it never states that .tf is the SPICE transfer-function analysis directive, and it offers no differentiation from the many sibling directive-inserters (prepare_ac, prepare_op, prepare_dc_sweep). Purpose is inferable but vague to an agent unfamiliar with SPICE dot-commands.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the ~15 prepare_* directive tools. The agent must guess whether it needs this or prepare_ac/prepare_op from the branch name alone.

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