run_hfss_optimization_job

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

With no annotations, the description carries the full burden for behavioral disclosure. It usefully states that the tool 'never overwrites the source project', a key safety trait. However, it does not disclose other side effects such as simulation execution time, resource usage, or whether the job can be rerun, leaving significant behavioral gaps.

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 exceedingly concise: a two-sentence statement that front-loads the action ('Run HFSS trials') followed by the most critical behavioral caveat. No words are wasted, and the structure is clear and scannable.

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 a single parameter, no annotations, and an output schema, the description is too sparse. It does not explain what the output represents, how job_id relates to the trials, or what happens when the job completes. The context of the HFSS optimization workflow is only hinted, making this insufficient for an agent to fully understand the tool's role.

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 schema has one parameter (job_id) with 0% description coverage, and the tool description does not mention job_id at all. The meaning is only inferable from the tool name (run_hfss_optimization_job) as the identifier of the optimization job to execute. The description fails to compensate for the lack of schema-level parameter documentation.

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 'Run HFSS trials' clearly identifies the action (run) and resource (HFSS trials), and the additional detail about not overwriting the source project clarifies the tool's behavior. It distinguishes from sibling tools like 'create_hfss_optimization_job' by focusing on execution, though it could be more explicit about running a specific optimization job by ID.

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 provides a prerequisite (ANTENNA_MCP_ALLOW_SIMULATION=1) but does not explain when to use this tool versus alternatives. It lacks guidance on selecting this tool over siblings like 'run_antenna_modeling_job' or 'build_hfss_project', offering no exclusions or context for decision-making.

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