Mark seams on edges by index or from sharp edges, clearing existing seams when needed for UV mapping.
标记缝合边：按边索引，或从锐边生成；clear 先清空。
| Name | Required | Description | Default |
|---|---|---|---|
| clear | No | ||
| edges | No | ||
| object | Yes | ||
| from_sharp | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions clearing existing seams but does not detail side effects like overwriting previous selections or the exact behavior of the clear flag.
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 a single concise sentence that conveys the core functionality without 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?
Given the simplicity of the operation and the schema, the description is sufficient. It does not explain return values, but none are expected for a mutating operation.
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 implicitly covers edges (by index), from_sharp (from sharp edges), and clear (clear first). The object parameter is not mentioned but is self-explanatory from the schema. Overall, the description adds meaning to all parameters.
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 (mark seam edges) and the method (by edge index or from sharp edges), providing a specific verb and resource. It distinguishes itself from other mesh operations.
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 mentions the clear option and the two marking modes but does not explicitly state when to use this tool versus alternatives. It gives some context but not a clear 'use when' directive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.