mesh_create

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

With no annotations, the description carries full burden. It explains that executing 'meshing operations defined in the mesh sequence' and returns status, but does not disclose side effects, error conditions, or blocking behavior. Adds some context about defaults but lacks depth.

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 clear header and structured argument list. Each sentence is informative, though the 'Args' section could be integrated into the main body for slightly better flow.

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 2 parameters and no output schema, the description covers the basic functionality and return status. However, it lacks information on prerequisites (e.g., existing mesh sequence), error handling, or integration with other tools.

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 description includes an 'Args' section explaining each parameter's meaning and default behavior, compensating for the 0% schema coverage. It adds value beyond the raw schema by clarifying default actions for null mesh_name and model_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?

The description clearly states the tool's purpose: 'Run a mesh sequence to generate the mesh.' It specifies the action (run) and resource (mesh sequence), and distinguishes from siblings like mesh_info or mesh_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?

No explicit guidance on when to use this tool vs alternatives or prerequisites. The description does not mention when not to use it or provide alternative tool names for similar tasks.

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