model_sweep

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutating nature is known. The description adds the default rectangular profile behavior and the requirement that section must be an existing shape name, but does not explain side effects like modifications to the original spline or failure handling.

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, front-loaded with the action, and covers key points in two sentences. The bilingual format adds some redundancy but remains 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?

For a simple mutating operation with no output schema, the description covers the essential behavior: the action, default behavior, and a critical constraint. It does not detail error handling or prerequisites beyond the spline path implication, but these are minor gaps.

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 100%, so baseline is 3. The description adds meaning beyond the schema by specifying the default profile when section is omitted and emphasizing that section must be an existing shape name, which is useful for correct invocation.

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 operation: sweeping a section profile along a path spline by adding a Sweep modifier. It uses a specific verb and resource, and implicitly differentiates from sibling modeling tools like extrude, lathe, and loft by describing a unique mechanism.

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 provides clear context for when to use this tool (when a sweep along a path is needed) but does not explicitly name alternatives or exclusions. It implies usage rather than giving direct when-to-use/when-not-to-use guidance.

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