rhino_create_sweep1

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

Annotations indicate a mutation (readOnlyHint=false) but provide no further behavioral details. The description does not disclose that the tool creates a new object, that it requires existing curves, or any side effects. It carries little beyond the annotation, so it fails to add meaningful behavioral context.

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: two sentences, with the core action front-loaded and the use cases in a second sentence. No fluff or repetitive details.

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 gives enough to select the tool but omits details about the output (though an output schema exists) and prerequisites such as having valid curves. It touches on parameters but not thoroughly. It is minimal but not entirely inadequate.

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?

The description clarifies the roles of the parameters by calling the rail a 'rail curve' and the sections 'cross-section curves', adding some semantic value beyond the schema's generic GUID descriptions. However, schema description coverage is 0%, so the description should compensate more, but it does not explain name, layer, or closed options.

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 sweeps one or more cross-section curves along a single rail curve, specifying the verb and resource. It gives concrete examples (moldings, pipes). It implicitly distinguishes from sweep2 by mentioning 'single rail', but does not explicitly name that sibling though many creation tools exist.

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 offers practical use cases ('moldings, pipes with varying cross-sections') providing some context for when to use it. However, it does not mention when not to use it or explicitly point to alternative tools like sweep2 or loft, so usage guidance is implied rather than explicit.

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