clear

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

With no annotations at all, the description carries the full burden; it does signal that this is a destructive bulk-removal ('Removes every block') rather than a fill, which is the most important trait. However, it says nothing about reversibility/undo, whether the region is inclusive of boundary coordinates, whether it requires the design to be open, or what happens to blocks outside the box.

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 sentence with the destructive action front-loaded and the clarifying examples carried in a short parenthetical. No filler and nothing is buried.

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?

An output schema exists, so return values need not be explained, but for a 7-required-parameter destructive mutation with no annotations and no per-parameter schema descriptions, the description is thinner than ideal. It conveys intent and the rough meaning of the coordinate set, but leaves region semantics and safety context to inference.

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 coverage is 0% and parameters are named only X1/Y1/Z1/X2/Y2/Z2 with no titles beyond those names, so the description is doing real work by indicating that the six integers define a three-dimensional box region and that 'design' selects the target. It still does not clarify inclusivity of the corners, coordinate units, or the expected format of the 'design' identifier.

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?

States a specific verb and resource: 'Removes every block in a box', with a parenthetical that clarifies the operation (doors, windows, hollowing out). An agent can distinguish this from siblings like set_block, replace, or box, though the description never names those alternatives explicitly.

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 parenthetical examples (doors, windows, hollowing out) imply when to reach for this tool, but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative. Usage has to be inferred from the examples rather than stated.

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