rhino_subd_sweep1

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

No annotations are present, so the description must disclose behavior. It only says 'Create a SubD sweep', which indicates a mutating geometry operation, but it does not explain what inputs are required (e.g., a rail and profile), whether it operates on the current selection, or what side effects occur. This is a significant transparency gap.

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 main sentence is concise and front-loaded, clearly naming the operation. However, the 'Args: controller...' line is redundant because the schema has no parameters and it contributes no useful guidance. The description is short but not every sentence earns its place.

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?

With no schema parameters and no annotations, the description must explain how to call the tool, but it does not state what geometry must be selected or what defines the rail/profile. The existence of an output schema does not cover these invocation details. This is incomplete for a construction tool of this complexity.

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 input schema is empty, so the 0-parameter baseline of 4 applies. The description's 'controller' line is not a schema property and adds no parameter information. No further parameter documentation is needed.

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 clear verb and object: 'Create a SubD sweep along one rail curve.' The phrase 'one rail curve' distinguishes it from rhino_subd_sweep2, so an agent can infer the singular-rail scope.

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 explicit when-to-use guidance or alternatives are mentioned. The phrase 'along one rail curve' implies a single-rail operation but does not contrast with sweep2 or list prerequisites. This is implied usage at best.

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