Loft

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this is a non-destructive, non-idempotent mutation. However, the description adds no further behavioral context such as what bodies are created or modified, how operation modes (new_body, join, cut, intersect) affect outcomes, or any side effects. It only restates the tool's purpose.

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 sentence with no waste, but it is under-specified for a tool with three parameters and multiple operation modes. Appropriately sizing the description would require including key usage or behavioral details, so its extreme brevity is a liability rather than a virtue.

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 complexity of a loft operation with an operation enum and target body option, and the absence of an output schema, the description omits critical context. It does not explain how the operation parameter affects the result, nor does it mention the target_body_name restriction warning that appears in the schema, leaving an agent without enough guidance for correct invocation.

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 67%, with target_body_name and profile_sketch_names having descriptions, while the operation enum lacks a description. The tool description itself provides no parameter semantics at all, failing to compensate for the moderate coverage gap. It adds no meaning beyond what the schema already conveys.

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 states a specific verb and resource: 'Loft between two or more sketch profiles.' This clearly conveys the core operation, distinguishing it from other modeling tools like extrude or sweep, though it does not explicitly name alternatives. The scope is well understood for a CAD agent.

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 when-to-use guidance or alternatives are provided. The description neither mentions when loft is preferred over siblings like extrude, sweep, or revolve, nor does it outline prerequisites or conditions for use. It merely states what the tool does.

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