Start Tidy3D simulation / 启动 Tidy3D 仿真

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

Annotations indicate a mutating operation (readOnlyHint=false), but the description adds behavioral context: it only starts when conditions are met, implying a gate check. It also mentions cost implications via FlexCredits, which goes beyond the schema and annotations.

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?

One concise bilingual sentence, efficiently conveying the gating conditions. The action is in the title, and the description focuses on when to start, which is appropriate and not redundant.

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?

With a full output schema and 100% parameter coverage, the description covers the essential decision logic. It does not explain the 'cloud gate' in detail, but that may be a global setting known to the agent. Overall sufficient for correct invocation.

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 covers each parameter individually, but the description ties them together: confirm_start must be true, max_flexcredits is the budget limit, and the cloud gate condition. This relational meaning adds value beyond the schema definitions.

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 title explicitly states 'Start Tidy3D simulation' and the description clarifies the action is to start a task, with conditions. It is clearly distinct from siblings like estimate_task_cost or upload_simulation, as it is the only tool that launches the simulation.

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 concrete preconditions: explicit confirmation, cloud gate, and cost within max_flexcredits. This tells the agent when it is appropriate to call the tool (after validation and cost estimation), though it does not explicitly name alternatives or exclusions.

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