generate_mesh

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

Annotations already indicate destructiveHint=true, but the description does not disclose what gets destroyed or overwritten when generating a mesh. It adds one input dependency (enhanced_refinement requires relative_element_size) but no behavioral context beyond what annotations provide.

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 two short sentences with the core action front-loaded in the first sentence and the parameter dependency in the second. There is no filler or redundant information.

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?

Despite having an output schema, the description lacks usage context, side-effect disclosure, and meaningful parameter semantics. It leaves the agent without enough information to know when to invoke the tool or what consequences to expect.

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 description coverage is 0%, so the description needed to explain the two parameters. It only names relative_element_size as a factor and states a constraint for enhanced_refinement, without defining what enhanced_refinement does or how the element size factor behaves.

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 action 'Generate the mesh' with a specific resource, and it distinguishes the tool from sibling tools, none of which target mesh generation. The optional relative element size factor is also mentioned, further clarifying scope.

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 when the user wants to generate a mesh, but it provides no explicit guidance on when to prefer this tool over alternatives or when not to use it. The only additional usage-related note is the parameter constraint, which is not about tool selection.

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