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

Annotations already indicate read-only behavior, so the description does not need to cover that. It adds valuable behavior beyond annotations: namespace defaulting, block states for block identifiers, and the critical warning that invalid identifiers fail silently in-game. This is meaningful operational context.

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?

Three sentences with no wasted words. The main function is stated first, then the block-specific detail, and finally the usage warning. Every sentence earns its place and the critical guidance is front-loaded.

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 simple two-parameter tool with no output schema, the description covers what the tool does, the categories it recognizes, the special case for blocks, namespace handling, and the consequence of invalid input. An agent has enough to call it correctly and interpret the result sufficiently.

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 100%, so the baseline is 3. The description adds extra semantic value by explaining the namespace default ('An identifier without a namespace is treated as minecraft:') and reinforcing the version default behavior through context, going beyond the schema examples.

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 states a specific verb (verify), a precise resource (minecraft: identifier existence and kind), and enumerates the categories it covers. It is clearly distinct from sibling validation tools, which target commands, JSON, scripts, or feasibility.

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 description gives an explicit when-to-use directive: 'Verify every identifier here before writing it.' This makes the intended invocation context clear. It does not explicitly name alternatives or exclusions, but none of the sibling tools overlap closely enough to require that.

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