rhino_stack_floors

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

The annotation readOnlyHint=false already signals mutation. The description meaningfully adds behavior: copies are placed along world +Z, the source sits at level 0, and copies populate levels 1..floor_count, clarifying the non-destructive nature and exact placement semantics.

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 tight: two sentences that state the core operation, the direction, the spacing, and the level semantics. The architectural shortcut line earns its place by immediately signaling intended usage.

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 creation tool with a rich input schema and an output schema present, the description covers the essential behavior. The only missing context is why to prefer this over rhino_array_linear or rhino_replicate_along_curve, but that is more of a usage-guidance gap.

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 already documents each parameter well, including floor_count meaning 'additional floors' and floor_height as Z spacing. The description reinforces this by stating the source is level 0 and copies occupy levels 1..floor_count, which removes ambiguity about whether the source counts as one of the floors.

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: "Replicate a source object N times along world +Z with constant spacing." It also includes the architectural metaphor "stack this slab N floors high," making the tool's niche immediately recognizable among the many array and duplication siblings.

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 description clearly states the intended use case: an architectural shortcut for stacking a slab N floors high. It implies this is for vertical floor replication rather than generic arrays, but it does not explicitly name alternatives like rhino_array_linear or explain when to choose this over them.

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