Save a world region to a schematic file

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

With no annotations, the description carries the behavioral disclosure burden. It communicates the core outcome and the useful detail that block entities are included. However, it does not mention overwrite behavior, file path constraints, or whether the operation is non-destructive to the world, though 'copy' implies it is.

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 focused sentence that front-loads the core action and adds only the essential detail about block entities. There is no redundancy or filler.

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 five-parameter tool with no output schema or annotations, the description gives enough to attempt a call but omits defaults, overwrite behavior, coordinate boundary semantics, and return behavior. It is adequate but not thorough.

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 only 20%, with only 'world' described. The description compensates by clarifying from/to as a box, mapping the format enum to .schem (Sponge v3) or .nbt (structure), and identifying path as the output file. It still leaves gaps around format defaults, path semantics, and coordinate inclusiveness.

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 operation: copying a box from the world into a .schem or .nbt file, with block entities included. It distinguishes this from paste_schematic by direction, though it does not explicitly separate it from the similarly named schematic_write.

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?

There is no guidance on when to use this tool versus any sibling such as paste_schematic or schematic_write. The description implies a saving use case but does not state prerequisites, exclusions, or alternatives.

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