blender_create_mesh

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

Annotations already mark the tool as non-readOnly and non-idempotent, and the description's 'Create' is consistent with that. However, the description adds no extra behavioral context such as scene placement, name-collision behavior, or whether the new object becomes active/selected.

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?

Two short sentences plus a focused code block; every clause adds information, and the face-loop clarification is directly useful. There is no filler, repetition, or unnecessary detail.

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?

It covers the face indexing rule well but leaves the vertex coordinate convention implicit and does not describe scene placement or optional parameter behavior. Given 7 parameters and no output schema, the description is adequate for a simple create call but not fully self-sufficient.

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 usefully clarifies the `faces` parameter, explaining zero-based vertex index loops and triangle/quad lengths. It does not explain the expected structure of `vertices` (e.g., [x, y, z] lists) or the semantics of `collection`, `material`, and `location`, and the schema itself only documents `response_format`, leaving most parameters without explanatory text.

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 uses a specific verb and resource ('Create a mesh object') and qualifies it with 'from explicit vertex and face data,' which clearly distinguishes it from primitive/operator-based mesh creation siblings like blender_add_primitive. It identifies exactly what the tool does.

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 phrase 'from explicit vertex and face data' implies this is for custom geometry rather than primitives or editing, but the description does not name alternatives or state when not to use it. Usage context is present only by implication.

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