cst_antenna_helix

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions creating components but does not indicate whether it modifies existing geometry, requires an open project, automatically adds ports, or has any destructive side effects. Key behavioral context is missing.

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 concise sentences that are front-loaded with the purpose. No unnecessary words or repetition.

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 creation tool without an output schema, the description lacks important context: coordinate system, units, effect on existing geometry, port creation, or return value. Given the tool's complexity, more detail is needed for a complete understanding.

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?

All three parameters (num_turns, ground_type, frequency_ghz) are described in the schema (100% coverage). The description adds overall context but does not enhance understanding beyond the schema's own descriptions, so baseline 3 is appropriate.

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 it creates an axial-mode helical antenna for circular polarization and lists the generated components (helix coil, ground plane, feed). This distinguishes it from other antenna types like cst_antenna_dipole or cst_antenna_spiral.

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 implies usage for circular polarization but does not explicitly state when to use a helix over alternatives like spiral antennas. No guidance on when not to use or which tool to choose instead is provided.

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