cst_set_floquet_port_advanced

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits like prerequisites (e.g., existing Floquet port), side effects, or error handling. Users are left unsure if this modifies an existing port or creates new settings.

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, front-loaded with purpose, no fluff. Every sentence adds value. Appropriate length and structure.

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 full schema coverage and lack of output schema, description covers purpose and parameters. However, it lacks context on prerequisites (e.g., existence of a Floquet port) and return values, which are important for a configuration tool.

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?

Input schema has 100% coverage with descriptions for all three parameters. Description mentions they control modes and scan angle but adds no extra meaning beyond schema. 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?

Description clearly states the verb 'Configure' and resource 'advanced Floquet port settings'. It distinguishes from sibling tools like 'cst_add_floquet_port' by focusing on advanced settings. Mentions specific controls (number of modes and scan angle) and context (periodic structures, phased array).

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?

Description implies this tool is for advanced configuration after adding a Floquet port, but does not explicitly state when to use it vs alternatives. Siblings include basic port creation, so guidance on sequencing or prerequisites would improve clarity.

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