Permanently convert all mesh faces to triangles when the triangulated topology must be stored in the blend file, ensuring the geometry is triangulated for downstream use.
Convert every face to triangles, permanently.
Usually unnecessary: exporters triangulate on the way out. Use this only when the triangulated topology itself must live in the blend file.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the permanent, irreversible nature of the operation ('permanently'), which is a key behavioral trait. It doesn't mention whether it modifies the object in place or other side effects, but for a simple mesh operation, this is adequate. The permanence disclosure goes beyond the schema and is valuable context.
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 sentences, front-loads the core action first, then adds usage guidance. Every sentence earns its place, with zero fluff. It is concise and well-structured.
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 a simple one-parameter tool, the description covers the main action and usage guidance. However, it leaves the 'name' parameter unexplained and does not mention any prerequisites (e.g., the object must be a mesh). Given no annotations or output schema, this is a notable gap that prevents full self-sufficiency for the agent.
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 schema has a single parameter 'name' with zero description coverage. The description does not explain what 'name' refers to (presumably the mesh object name). While the tool name implies it, the agent gets no explicit guidance on what this parameter expects. Since the schema provides no description, the description must compensate, and it fails to do so.
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: 'Convert every face to triangles, permanently.' It specifies the resource (every face of a mesh) and the operation (conversion to triangles). It also distinguishes itself from the broader mesh modification siblings by focusing on triangulation, making its purpose unambiguous.
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?
Excellent usage guidance. It explicitly warns 'Usually unnecessary: exporters triangulate on the way out' and gives the specific condition for use: 'Use this only when the triangulated topology itself must live in the blend file.' This tells the agent exactly when to choose this tool over simply relying on export settings, and implicitly mentions the alternative (exporters).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.