mc_set_block_glow

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

No annotations provided, so description carries full burden. It reveals version-specific behavior (1.19 vs 1.21.11) and the ability to add or remove highlights. Lacks details on persistence or side effects, but sufficient for a simple highlight tool.

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, front-loaded with core purpose, efficient. No wasted words.

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 tool with no output schema and 4 parameters, description covers purpose, usage, version-specific behavior, and cross-tool references. Complete and self-contained.

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 25% (only glow described). Description mentions position parameters implicitly via 'block in-world' and cross-reference to mc_nearby_blocks, but does not add detailed parameter semantics. Some compensation but not full.

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?

Description clearly states the tool highlights a block in-world or removes the highlight, specifying version-dependent visual behavior. It distinguishes itself from sibling mc_clear_block_glow.

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?

Explicit guidance: useful for pointing out specific blocks, recommends pairing with mc_nearby_blocks for position finding, and directs to mc_clear_block_glow for clearing all highlights.

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