generate_2d_mesh

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

No annotations are provided, so the description must disclose behavior. It only says 'Generate a 2D mesh' and does not mention that it invokes a Gmsh subprocess, can be time-consuming, or has side effects like creating mesh files. The output format and dependencies (e.g., valid geometry_id) are not described, leaving a significant transparency gap.

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 a single, concise sentence (15 words) that starts with action and object. It contains no filler and effectively communicates the core purpose.

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 12 parameters and no annotations, the description should provide more high-level context about prerequisites, runtime, and workflow position. It mentions geometry_id but does not explicitly state that the geometry must be generated first or that this mesh is required for subsequent solver calls. The output schema exists, mitigating the need to describe return values, but gaps in workflow context remain.

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 input schema covers 100% of parameters with detailed descriptions (e.g., domain_size, growth_rate, target_y_plus). The tool description adds only the workflow context and mentions geometry_id, which is already in the schema. Since the schema does the heavy lifting, the description provides marginal added value, fitting the baseline of 3.

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 clearly states the tool's function: generating a 2D mesh from a geometry_id for NeuralFoil or SU2 workflows. It uses a specific verb ('Generate') and resource ('2D mesh'), and the mention of geometry_id distinguishes it from geometry-generation and solver tools. The sibling tools reinforce its role as the meshing step in the pipeline.

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 implies the tool is used after generate_airfoil_geometry (via geometry_id) and before solver tools (for NeuralFoil or SU2 workflows). It provides context but does not explicitly state when not to use it or name alternatives. The guidance is clear enough for an agent familiar with the workflow, but lacks explicit exclusions.

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