femm_create_mesh

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

With no annotations, the description carries the full burden and does well: it discloses the hidden side effect that the model is saved first, that no element count is returned by FEMM 5, and how to interpret meshing errors (open regions, overlapping lines). It omits what the tool actually returns on success.

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?

Front-loaded with the core action and scope in the first clause; the parenthetical about solve timing is mild padding but the rest earns its place. No redundant restatement of the name.

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?

For a no-annotation, no-output-schema, one-param tool, the description covers the important behavioral traits (implicit save, no return count, error interpretation). It is only short on session semantics and what a successful call actually returns.

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 single 'session' parameter has 0% schema description coverage, and the description never mentions sessions or how to target a non-default one. The description adds no meaning beyond the bare schema property name.

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?

States a specific verb+resource ('Mesh the model') and pins the scope precisely with 'without solving', naming the underlying API call (xi_createmesh) and the goal ('check that meshing succeeds'). This clearly separates it from femm_solve and femm_smartmesh in the sibling list.

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?

Explains the use case (verify meshing succeeds before/instead of solving) and implicitly routes the agent to femm_solve when element counts or results are actually wanted. It doesn't state exclusions as explicitly as 'use X instead' but the when-to-use context is clear.

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