rhino_join

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds useful context by specifying that objects must be 'adjacent' (touching) to join. It does not disclose failure behavior (e.g., what happens when objects are not adjacent), but with annotations covering the safety profile, this is acceptable.

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?

A single, front-loaded sentence with no wasted words. It states the action and the input type compactly. It loses a point only because it fits so little information into its brevity.

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 single-parameter tool with an output schema, the definition is largely adequate. However, it omits practical details an agent needs: that objects must share endpoints/tolerance, the result of non-adjacent inputs, and the relationship to the destructive hint (that originals are consumed). These are moderate gaps for a mutation tool.

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 schema itself describes the sole parameter as 'GUIDs of curves/surfaces to join' and enforces minItems 2, so the schema carries most of the burden despite the 0% coverage signal. The tool description repeats the target types but adds no new syntax, format, or selection guidance beyond 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 states a specific verb ('join'), a resource ('curves or surfaces'), and the outcome ('into a single object'). It is clear on its face, and the phrase 'single object' helps differentiate it from grouping. However, it does not explicitly distinguish itself from rhino_group or the boolean operations, which produce similar aggregate results, so it stops short of a 5.

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 guidance is given on when to use this tool versus alternatives. An agent could reasonably confuse rhino_join with rhino_group, rhino_boolean_union, or rhino_explode (the inverse), and the description provides no routing information, prerequisites (e.g., objects must share endpoints), or exclusions.

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