create_hfss_optimization_job

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

The description discloses that the tool copies an existing project and creates an isolated job, which implies the original project is not mutated. However, there are no annotations, so the description carries the full burden, and it fails to mention prerequisites, lifecycle implications, or whether any persistent state is created beyond the copy.

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?

The description is a single concise sentence that front-loads the action ('Copy') and avoids extraneous words. It is appropriately sized for the tool's basic 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?

Despite the tool's complexity (black-box optimization, opaque request object, no annotations), the description is too terse. It does not explain required inputs, how the isolation works, what 'prepare black-box optimization' entails, or what the caller should expect. An output schema exists but is not provided, so the description must carry more weight.

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?

The input schema has a single generic 'request' object with additionalProperties true and no field descriptions, giving 0% schema coverage. The description adds no meaning about what the 'request' should contain, leaving the agent with no guidance on how to construct a valid request.

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 a specific action: copying an existing HFSS project into an isolated job and preparing black-box optimization. It distinguishes this creation/preparation step from sibling tools like run_hfss_optimization_job and build_hfss_project.

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 the tool is used in an optimization workflow, but it does not explicitly state when to use it versus alternatives, nor does it mention related steps like running the optimization job. No exclusions or alternative tool references are provided.

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