moldsim mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It compensates well by detailing exactly what data is returned (Cross-WLF viscosity model, 2-domain Tait PVT, thermal/mechanical data) and listing the constrained set of available materials, effectively communicating scope and output format.

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?

Three dense sentences with zero waste: sentence 1 states purpose, sentence 2 details return values, sentence 3 lists valid inputs. Well front-loaded with the action verb and appropriately sized for the tool's complexity.

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 rich input schema (100% coverage) and absence of output schema, the description adequately compensates by describing return data types (Cross-WLF, PVT models) and valid material inputs. Only missing safety/performance annotations prevent a 5.

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?

Despite 100% schema coverage (baseline 3), the description adds significant value by enumerating the specific available materials (abs-generic, pp-homo, etc.), which acts as implicit enum documentation beyond the schema's generic 'Material name, family, or ID' description. This concrete list helps agents select valid inputs.

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?

Description uses specific verb 'Look up' with clear resource 'material properties' and domain context 'injection molding simulation'. It effectively distinguishes from siblings like compare_materials (which implies multiple materials) and generate_dfm_checklist (which is procedural rather than data retrieval).

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?

While the description provides specific domain context that implies when to use it (when you need injection molding property data), it lacks explicit guidance on when to prefer sibling tools like compare_materials or validate_process_parameters. No explicit exclusions or alternatives are named.

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