convert_surfaces_to_solid

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

With no annotations, the description carries the disclosure burden and does reasonably well: it explains the staged behavior (stitch → patch → close), the closed-shell shortcut, that it reports each step plus resulting volumes, and that it surfaces open edges it could not close with mm coordinates. It omits what happens to the original surface bodies after conversion (replaced, consumed, or left behind), which matters for a shell-closing operation.

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?

Front-loaded with the outcome and scenario before any mechanics, and the Args block is scannable. A few phrases ('so no mass and no booleans') are color rather than instruction, and the Args formatting is slightly verbose, but nothing is redundant or misleading.

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 4 optional params, 25% schema coverage, no annotations, and an output schema that already covers return values, the description supplies exactly what's missing: the failure mode (unclosed open edges), unit conventions, grouping strategy, and the run-context prerequisite. An agent can invoke this correctly from the description alone.

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 coverage is only 25% (only 'instance' is documented), but the Args block compensates strongly: work_surfaces accepts 'all' or numbered groups '1,2,5' with a rationale, tolerance is defined as the largest gap to stitch in mm, and patch_holes is explained as filling loops of open edges with a boundary patch. Only 'instance' is left to the schema, so the description adds real meaning over the raw property names.

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?

States a specific verb+resource ('Turn surfaces into solids') and immediately grounds it in the real scenario: imported vendor models (x_t, IGES, STEP) arriving as faces with no volume, mass, or boolean capability. It also enumerates the concrete operations (stitch, patch holes, close shell) so an agent can distinguish this from import_step or generic feature tools without opening the schema.

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?

Gives clear operating context: 'Run it in the part that holds the surfaces' and converts 'one group at a time (e.g. one component of a multi-part import)'. That establishes the prerequisite and a sensible batching strategy, but it never names an alternative sibling (e.g. import_step for fresh imports) or states when-not to use it, so it stops short of full routing guidance.

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