sweep

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

With no annotations, the description carries the full behavioral burden. It adds useful constraints like 'additive pipe' and 'in the same body,' but it does not disclose permissions, failure conditions, reversibility, or whether the operation requires an active body/document.

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 compact and front-loaded: purpose first, then parameter definitions. Every line adds useful information without repetition or 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 5-parameter CAD feature with no output schema and no annotations, the description gives enough to understand the operation and most parameters. It still lacks coverage of the 'name' parameter and broader prerequisites or side effects, but it is largely complete for 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 0%, so the description must compensate. It defines profile, spine, mode, and transition, including allowed values for mode and transition, but it omits the 'name' parameter entirely.

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 CAD verb and resource: 'Sweep a profile sketch along a spine sketch (additive pipe).' This clearly distinguishes the tool from generic shape operations and identifies the exact input entities.

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 by describing the sweep operation and its inputs, but it does not explicitly compare against alternatives such as loft, revolve, or pad. There is no when-to-use or when-not-to-use guidance beyond the operation name.

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