aedt_insert_far_field

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits such as whether it modifies the current design, error handling, or if re-insertion overwrites an existing setup.

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 extremely concise at 6 words, which is acceptable for simplicity, but it sacrifices essential details. It lacks structure to convey multiple aspects.

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 the expected complexity of inserting an HFSS far-field setup (likely requiring parameters like frequency, sphere radius, etc.), the description is severely incomplete. It does not mention return values or state changes, and an output schema exists but is not described.

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 defines a single generic 'kwargs' parameter with 0% documentation coverage in the schema. The description does not explain what kwargs should contain, leaving the agent with no guidance on how to configure the far-field setup.

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 'Insert an HFSS infinite-sphere far-field setup.' with a specific verb ('Insert') and resource ('HFSS infinite-sphere far-field setup'), distinguishing it from sibling tools like 'aedt_insert_near_field'.

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 no guidance on when to use this tool versus alternatives (e.g., near-field setup), nor any prerequisites or scenarios to avoid.

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