sculpt_extract_face_set

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

No annotations are provided, so the description must fully convey behavioral traits. It only states that the tool extracts a face set and has thickness for solidify. Missing details include what happens to the original mesh, whether the operation is destructive, prerequisites (e.g., in sculpt mode), and any side effects.

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 very concise: three short sentences plus an args list. The purpose is front-loaded, every sentence adds value, and there is no redundancy.

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 no annotations, no output schema, and 3 parameters with minimal schema details, the description is lacking. It omits information about the resulting object (e.g., new object name, location), selection behavior, and differentiation from similar tools like 'sculpt_extract'.

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 compensates with an 'Args' block. It adds meaning: mesh_name is the mesh object name, face_set_id starts at 1, thickness is for solidify. However, it does not explain what a face set is or how to obtain the ID, and mesh_name lacks context (e.g., exact naming requirements).

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 first sentence clearly states the action: 'Extract a face set from a sculpted mesh as a separate object.' It also lists use cases. However, it does not explicitly differentiate from the sibling 'sculpt_extract' tool, which may have a similar purpose.

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 provides clear usage context: 'Useful for creating accessories, clothing pieces, or separating features from a base sculpt.' This tells when to use the tool, but it does not mention when not to use it or suggest alternatives.

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