rhino_join

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the basic action but does not disclose whether joining is destructive to the original objects, whether there are connectivity or tolerance requirements, how the operation affects the Rhino document, or what happens when the selection is invalid.

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 short and front-loaded with the core verb and object. The Args block is minimal and mostly unnecessary, but it does not add meaningful bloat. Overall it is efficient without being under-specified to the point of confusion.

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 join operation with an empty input schema and an output schema present, the description provides the essential action and object types. However, with no annotations and no guidance on preconditions, tolerances, or sibling-tool routing, an agent still has to infer several important details about successful 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?

The input schema has zero properties, so there are no undocumented parameters. The description's mention of 'controller: RhinoController instance' adds a small amount of context about how the tool is invoked, and the 0-parameter baseline applies here.

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 action ('Join'), the input scope ('selected surfaces, curves, or polysurfaces'), and the result ('into a single object'). It is specific enough to understand the tool's purpose, but it does not explicitly differentiate it from nearby siblings like rhino_merge_surfaces, rhino_group, or boolean union tools.

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 word 'selected' implies the precondition that the user must select objects before invoking the tool, which is useful context. However, it does not explicitly say when to prefer this tool over alternatives like boolean union, merge surfaces, or grouping, nor does it mention when not to use it.

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