rhino_tube

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

With no annotations, the description carries the full disclosure burden. It only says it creates a tube and returns a status/command dict, with no mention of document side effects, units, coordinate system, failure behavior, or whether the action is undoable.

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 organized into concise Args and Returns sections with no fluff. Every sentence contributes purpose or parameter meaning, though the controller line hints at an argument not present in the actual schema.

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 parameter definitions and return note are adequate for a simple shape-creation call. However, it omits when to use this vs alternatives, geometric constraints, units, and prerequisites, and the controller argument is not represented in the input schema.

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 define parameters, and it does: center x/y/z, outer_radius, thickness with the inner_radius formula, and height. It lacks constraints such as thickness < outer_radius and units, and it mentions a controller argument that is absent from the schema.

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 opens with a specific verb and resource: 'Create a hollow cylindrical tube in Rhino.' The 'hollow' and wall-thickness semantics distinguish it from a plain cylinder, but it does not explicitly differentiate from siblings like rhino_cylinder or rhino_pipe_from_curve.

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?

There is no guidance on when to use this tool versus the many shape-creation siblings. It does not state prerequisites, exclusions, or alternatives; the description only defines what the tool does.

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