add_lofted_solid

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

With no annotations, the description carries the full load and does so well: it discloses that 2 profiles give a ruled transition while 3+ blend smoothly, that centers may wander, the vertex-order twist hazard, and that the tool returns mass properties. It does not state permissions or whether the operation is reversible, which keeps it from a 5.

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?

Purpose is front-loaded in the first clause, and every following sentence adds a distinct constraint (ordering, length, twist). The heavy parenthetical asides make it denser than ideal, but no sentence is filler.

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 complex geometry tool with no annotations and no output schema, the description covers inputs, ordering rules, the ruled-vs-smooth distinction, and the return (mass properties). It is nearly complete, missing only failure modes or unit/permission caveats.

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 0%, so the description must compensate and it does: profiles_mm is explained as either a polygon of [x,y] pairs in Front-plane coords or a round {center_mm, diameter_mm} section, and heights_mm is described as a strictly increasing +Z offset list of equal length starting at 0.

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 (Loft/blend) and resource (closed profiles on parallel planes along +Z), with enough detail to distinguish it from siblings like add_swept_profile and add_revolved_profile 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 one concrete prerequisite ('Use new_part first') and implicitly frames the tool as a solid-creation step, but never states when to choose loft over the neighbouring sweep/extrude/revolve tools. Usage is implied rather than routed.

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