cst_get_group_delay

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

No annotations are provided, so the description should disclose behavioral traits. It states it computes from S-parameter phase, implying a read operation on existing data, but does not specify whether a prior simulation is required, if results are stored, or any side effects. Some transparency but incomplete for a tool with no 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?

Two sentences: the first succinctly defines the tool's action and formula, the second provides application context. No redundant or extraneous information. Front-loaded with the primary purpose.

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 only two parameters and no output schema. The description explains the core concept and use cases. However, it lacks details about the return value format (e.g., a single value or array) and any dependencies (e.g., requires solved project). Still, for its simplicity, it is largely complete.

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% with descriptions for both parameters. The main description does not add additional semantic meaning beyond the schema's 'input port number' and 'output port number'. The baseline of 3 is appropriate as the schema already handles parameter documentation.

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 computes group delay from S-parameter phase for a port pair, defines the formula, and gives specific use cases (UWB antenna and filter characterization). It distinguishes itself from sibling tools like cst_get_s_parameter_phase by focusing on the derived metric.

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 mentions 'useful for UWB antenna and filter characterization' implying context, but does not explicitly state when to use this tool versus alternatives like cst_get_s_parameter_phase or cst_get_impedance. No exclusions or prerequisites are provided.

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