cst_matching_create_lumped

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

No annotations provided, so description carries full burden. It only states what the tool does (generate code) without disclosing side effects, whether it executes the code, if it modifies existing components, or requires an open project. For a code-generation tool, this is insufficient.

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?

Description is a single concise sentence with no redundant phrases. It efficiently conveys the core function, though slight restructuring could improve clarity (e.g., separating the code generation aspect from the placement details).

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?

Given no output schema or annotations, the description should explain what the generated code does, its format, or any prerequisites. It lacks information about execution context, return value, or integration with CST, leaving significant gaps for an agent.

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 covers 100% of parameters with descriptions; the description adds minimal extra meaning (e.g., placing components as LumpedElement with series/shunt). Baseline 3 is appropriate as no additional semantic insight is provided beyond the schema.

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 generates CST VBA code to create a lumped-element matching network with explicit mention of components (inductor, capacitor, resistor) and placement as CST LumpedElement. This differentiates it from sibling tools like cst_matching_l_network or cst_matching_pi_network which target specific topologies.

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 guidance on when to use this tool versus alternatives (e.g., other matching network tools or lumped element tools). There is no mention of prerequisites, contexts, or when not to use it.

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