Clear / Dig Out Area

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

Beyond the annotations (destructiveHint=true), the description adds valuable behavioral details: digs top-down, skips non-diggable blocks, caps at 500 blocks, and includes a return summary with dug/skipped counts. This enriches the agent's understanding beyond the basic mutation flag.

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 and effective: a clear first sentence stating the operation, a single-sentence caveat about the cap, and a concise return type. No filler; every sentence earns its place.

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?

With six unannotated parameters and no output schema, the description covers what the parameters mean, the behavior (top-down, skip non-diggable), the size limit, and the return structure. It is fully sufficient for an agent to use the tool correctly.

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 input schema has zero descriptions for its six numeric parameters. The description compensates by explaining that the parameters are two corners defining a cuboid region, which gives full meaning to the coordinate pairs. It also clarifies the 500-block cap on the region size, adding crucial constraint context.

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 action ('Digs out (breaks) every non-air, diggable block') and the resource ('a cuboid region between two corners'). It distinguishes from siblings like minecraft_dig_block (single block) and minecraft_build_structure (construction) by specifying the region-based clearing use case.

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?

Provides explicit context for when to use it: 'for clearing land or hollowing out a room.' It implies this is for bulk removal rather than single-block digging, though it does not name alternative tools directly or provide exclusions.

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