set_block_nbt

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

No annotations are provided, so the description carries the full burden. It does not say whether existing NBT is overwritten or merged, whether the operation fails on non-block-entity blocks, whether a world must be loaded, or whether the change is undoable (a sibling undo exists). Only the SNBT format hint is disclosed.

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?

Two short lines with no padding and the example is front-loaded, which is good. However the brevity comes at the cost of under-specification rather than efficiency, and the embedded NBT snippet is cryptic without stating what it is an example of besides 'chest contents'.

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. For a five-parameter mutation tool with zero annotation and zero schema-description coverage, the description is thin: it omits prerequisites, overwrite semantics, and coordinate/name meaning that an agent needs to call it 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?

Schema coverage is 0% with five required parameters named only by bare titles. The description usefully illustrates the snbt format with a concrete SNBT example, but leaves x/y/z/name unexplained and never states that name is the block id or that the coordinates identify the target block entity.

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 action (attach NBT to a block entity) but never says it operates on the block at the given x/y/z coordinates, nor how it differs from siblings like set_blocks or fill. An agent can infer the general intent, but not the scope or the target of the operation.

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 instead of set_blocks, fill, or replace_blocks, and no prerequisites (e.g. the block must already exist and be a block-entity type such as a chest). The one example given is about data format, not usage selection.

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