fusion_sweep

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

Annotations indicate a non-read-only, open-world operation. The description adds value by specifying that the path must be an open sketch and the profile closed, and that the sweep follows the first curve of the path. No contradictions exist, and behavioral prerequisites are disclosed.

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?

Two concise sentences, no redundancy. The first sentence states the core action, the second provides essential prerequisites. Information is front-loaded and efficient.

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 primary workflow but omits details on optional parameters and return values. Given the tool's complexity (4 parameters, no output schema) and the presence of many sibling modeling tools, more context—like when to sweep vs. extrude—would improve completeness.

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?

With 0% schema description coverage, the description must compensate. It explains 'profile_sketch' and 'path_sketch' but does not clarify the 'profile' parameter (likely an index) or the 'operation' parameter (default 'new'). Two of four parameters lack meaningful explanation, leaving ambiguity.

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 the tool performs a sweep operation using a profile sketch and a path sketch, with specific instructions on how to prepare the sketches (open path, closed profile). This distinguishes it from other modeling tools like extrusion or revolve.

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 implies usage for creating a swept feature but does not explicitly state when to choose this tool over alternatives such as extrusion or loft. No exclusions or comparative guidance are provided, leaving the agent to infer context.

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