rhino_explode_block

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 operation and outcome but does not disclose whether the original block instances are deleted, how nested blocks are treated, or what happens if nothing is selected. For a mutating explode operation, this is a notable transparency gap.

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 a single sentence that states the action, target, and result without filler or repetition. It is appropriately sized for a zero-parameter tool.

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 zero-parameter tool with an output schema, the core action and target are present and the return value does not need explanation. However, the description is incomplete because it does not clarify how this tool differs from the similar rhino_block_explode sibling or hint at side effects such as destruction of the original block instance.

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 tool has zero parameters, so there are no parameter semantics for the description to add beyond the empty schema. The description's reference to 'selected block instances' usefully signals that the implicit target comes from the current Rhino selection.

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 names a specific verb ('Explode') and resource ('selected block instances') and states the result ('constituent geometry'), so the purpose is clear. It does not distinguish itself from the similarly named sibling rhino_block_explode, so it does not earn 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?

The phrase 'selected block instances' implies a prerequisite that blocks must be selected, but there is no explicit when-to-use guidance. It does not mention when not to use the tool or reference sibling alternatives such as rhino_block_explode or rhino_explode, leaving tool selection ambiguous.

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