sculpt_trim

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

With no annotations, the description carries the full burden. It discloses the auto-cleanup behavior and explains the structure of each trim type. However, it does not indicate whether the operation is destructive, if the original mesh is modified or replaced, or if undo is supported. Some behavioral details are missing.

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 concise and well-structured, with an introductory line, bullet-like list of trim types with their params, and a cleanup note. Every sentence provides useful information without 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?

The description covers the core functionality and parameter details, but lacks context on prerequisites (e.g., being in sculpt mode), expected outputs (though output schema exists), and side effects. Given the complexity, some additional context would be beneficial.

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%, but the description adds significant meaning by explaining each trim_type and providing detailed JSON format examples for plane, box, sphere, and custom. This goes well beyond the schema's basic types and defaults, making the parameter usage clear.

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 that the tool performs 'Boolean trim/cut operations for sculpting' and lists specific trim types (plane, box, sphere, custom). This distinguishes it from the general boolean_operation tool and other sculpt tools by specifying the sculpting context and the trim/cut focus.

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?

No guidance is provided on when to use this tool versus alternatives like boolean_operation or other sculpt tools. The description does not mention prerequisites, when to choose one trim type over another, or when this tool is preferable.

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