Write a JSON file summarizing CST solver settings, frequency range, S11, and efficiencies to a chosen path for result reporting and verification.
Write a single JSON file summarising solver, frequency range, S11 and efficiencies.
| Name | Required | Description | Default |
|---|---|---|---|
| out_path | Yes | ||
| target_frequency | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses that a JSON file is written and what it summarizes, but does not state whether an existing file is overwritten, whether a CST session must be connected, what permissions are needed, or any other operational constraints.
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 a single front-loaded sentence with no wasted words. It is appropriately concise, though its brevity contributes to gaps addressed in other dimensions.
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?
The tool has no annotations, 0% input schema description coverage, and is a write operation, yet the description does not compensate with parameter or behavioral details. While an output schema exists (so return values need not be explained), the input side and usage context remain under-specified.
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 0%, so the schema does not explain out_path or target_frequency. The description mentions none of the two parameters, leaving their purpose and expected values completely undocumented.
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 gives a specific verb ('Write') and resource ('a single JSON file') along with the summary contents (solver, frequency range, S11, efficiencies). It clearly distinguishes the tool from read-only siblings like cst_read_result_tool and cst_read_s11_tool, though it does not explicitly name alternatives.
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 states what the tool does but offers no guidance on when to use it versus alternatives (e.g., cst_export_ascii_tool, cst_export_touchstone_tool, or cst_read_result_tool). No conditions, prerequisites, or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.