mesh_create

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

No annotations exist, so the description must fully disclose behavior. It states the tool runs meshing operations and returns a status, but it omits critical details: whether it is destructive (overwrites existing meshes), requires a model to be loaded, has side effects, or is asynchronous. The lack of behavioral context is a significant 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 concise, with a one-line summary followed by parameter and return descriptions. No superfluous information. The structure (summary, Args, Returns) is clear and front-loaded.

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 tool's complexity (2 optional params, no output schema), the description is minimally complete: it explains the main action and parameter roles, but lacks details on return value format, error conditions, or interaction with other tools (e.g., mesh_info). The return 'Mesh generation status' is vague.

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?

Schema coverage is 0%, so the description must compensate. It does provide semantic value: mesh_name is described as 'Mesh sequence name (default: run all mesh sequences)' and model_name as 'Model name (default: current model).' This adds meaning beyond the schema titles and defaults, but details on allowed values or format are missing.

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 purpose: 'Run a mesh sequence to generate the mesh.' It specifies that it executes meshing operations from a sequence, which distinguishes it from sibling tools like mesh_info or mesh_list that only inspect or list meshes. The action verb 'run' and resource 'mesh sequence' are specific.

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?

Usage is implied from the purpose—'when you want to create a mesh by running a sequence'—but no explicit guidance on when to use this tool versus alternatives like mesh_info or mesh_list. No prerequisites or exclusions are mentioned, relying on the user to infer context.

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