build_mesh

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

With no annotations provided, the description carries the full burden of disclosing effects and preconditions. It discloses nothing about whether existing geometry is required, what state changes occur, or what the operation returns or modifies.

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 short, but this is under-specification rather than effective conciseness. The sentence restates the tool name and contains no distinct information that earns its place.

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 mesh-related siblings and an output schema, the description provides no context about model prerequisites, whether a geometry must exist first, or how this step fits into a larger workflow. An agent cannot determine the appropriate circumstances for invoking this tool.

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 parameter mesh_tag has 0% schema description coverage, and the description does not compensate by explaining its meaning or effect. The schema only provides a title and default value; the description adds no semantic value.

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 'Build the mesh.' simply restates the tool name and provides no additional specification of what building the mesh entails. It is a tautology rather than a substantive definition.

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?

There is no guidance about when to call this tool versus siblings like import_geometry, generate_model_java, or run_solver. No prerequisites, conditions, or alternative recommendations are provided, though the text is not misleading.

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