blender_mesh_from_data

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the primary effect—creating a mesh object from raw data—and the API method used, which is useful. However, it does not describe side effects on the current scene, validation of vertex/face data, or what happens on failure, so transparency is only partial.

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 compact sentences with the action and data source front-loaded. There is no filler, and the 'procedural geometry' note adds useful context without bloating the description.

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?

All parameters are documented in the schema, and the description clearly frames the tool's core purpose. Given the absence of annotations and output schema, though, the description does not fully cover contextual details such as whether the new object is added to the active collection, how invalid mesh data is handled, or what the agent should expect as a result.

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 100%, so the parameter schema already documents all six parameters. The description reinforces the meaning of vertices and faces through 'raw vertex/face data' but adds no new information about edges, location, or smooth_shade beyond what the schema provides.

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 states a specific verb ('Create'), a clear resource ('mesh object'), and the precise data source ('raw vertex/face data'). It also names the underlying API method mesh.from_pydata(), which makes the intent unambiguous and distinguishes it from siblings like blender_curve_to_mesh or blender_object_create.

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?

'Useful for procedural geometry' provides an implied use case, but there is no explicit guidance about when to use this tool versus the many sibling mesh tools, and no exclusions or alternative routing. The description gives some context but leaves the agent to infer the boundary between this and other creation/modification tools.

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