cst_add_floquet_port

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

No annotations provided, so description carries full burden. Only states 'Add a Floquet port' without disclosing side effects, prerequisites (e.g., periodic boundary needed), constraints (port number uniqueness), or return values. Minimal 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?

Single sentence, front-loaded with purpose. No wasted words, but could include more useful details without losing conciseness.

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?

No output schema exists, yet description does not hint at return value or success indicators. Lacks prerequisites, post-conditions, and behavioral traits. Incomplete for a tool with 3 parameters and no annotations.

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% and already describes each parameter. Description adds no extra meaning beyond schema (e.g., does not explain the physical significance of 'modes' or 'orientation'). Baseline 3 is appropriate as description does not reduce ambiguity.

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?

Description explicitly states 'Add a Floquet port' and lists example applications (FSS, metamaterials, phased arrays). This clearly distinguishes it from other port types like discrete, waveguide, or multipin ports, and from the advanced Floquet port settings tool (cst_set_floquet_port_advanced).

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?

Implied usage via 'for periodic structures...' but no explicit when-to-use or when-not-to-use. Does not mention alternatives or compare with sibling port tools. Guidance is present but not comprehensive.

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