Normalize local Tidy3D result / 归一化本地结果

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

The description only mentions the path restriction ('without arbitrary path access') but does not disclose side effects. Despite annotations indicating idempotent and non-destructive, readOnlyHint is false, implying potential writes, yet the description frames the operation as a read, which is inconsistent with the mutation implied by normalization. The description also omits whether a normalized artifact is written.

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 short (two sentences) and front-loads the security constraint, but it is bilingual, repeating the same information in English and Chinese. While not verbose, the lack of substantive content makes the conciseness less valuable—it is compact but shallow.

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 an output schema present, return-value details are not needed, but the description fails to explain the normalization workflow, when to call this versus read_normalized_artifact, or what side effects occur. Given the tool's role among siblings, this is a significant gap for an agent to invoke it correctly.

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 already documents workspace_path as a relative path under TIDY3D_MCP_WORKSPACE_DIR (100% coverage). The description adds that it reads JSON/HDF5 results, which gives file-format context, but this is minimal and does not explain formatting, encoding, or validation details beyond the schema.

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 says 'Read a relative Tidy3D JSON/HDF5 result' but the tool name is 'normalize_local_result', implying a transformation. It does not explain what normalization entails, and the read action overlaps with the sibling tool read_normalized_artifact, so an agent cannot distinguish this tool's core purpose from that sibling.

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?

No guidance is provided on when to use this tool versus alternatives like download_simulation_result or read_normalized_artifact. There is no mention of prerequisites, order in a workflow, or conditions that select this tool over its siblings.

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