rhino_replicate_along_curve

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

Annotations already indicate write operation (readOnlyHint=false). The description adds context about reorientation via align_to_tangent and endpoint inclusion, but does not disclose side effects (e.g., object creation, transformation persistence) beyond what is implied.

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?

Two short paragraphs with a clear first sentence stating the main action. No fluff, but the parameter explanation is somewhat embedded in a code-like style. Could be slightly more streamlined.

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 complex mutation tool, the description covers core behavior but omits output details (despite having an output schema), error conditions, or required object validity. Adequate for basic use but lacks thoroughness.

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 compensate. It explains two key parameters (align_to_tangent, include_endpoints) with behavioral details, but ignores count, curve_id, source_object_id, and doc_id. This partially compensates but leaves gaps.

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's purpose: 'Distribute copies of a source object along a curve at evenly-spaced parameters.' It uses specific verb+resource ('distribute copies') and distinguishes it from siblings like linear/polar arrays by focusing on curves.

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 on when to use this tool vs alternatives (e.g., rhino_array_linear, rhino_flow_along_curve). The description implies usage for curve-based replication but does not mention prerequisites or 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.