set_block

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

No annotations are provided, so the description must carry the full behavioral burden. It says the tool mutates the world, but it does not disclose overwrite behavior, required permissions, coordinate semantics, failure cases, or what happens when setting to air.

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 definition is a single front-loaded sentence with no wasted words. However, it is too terse for a five-parameter mutation tool, so conciseness comes at the cost of under-specification.

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 described. Still, for a five-parameter mutation tool with no annotations and no parameter descriptions, the definition omits critical context about design, coordinates, and replacement behavior.

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 0%, and all five parameters are required. The description adds only a small clue about the block parameter's accepted forms, leaving x, y, z, and especially design unexplained.

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 and resource: it puts one block, and it clarifies that the block may be a role, block state, or air. This is clearer than a tautology, but it does not distinguish the tool from nearby siblings such as replace or box.

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 set_block versus alternatives like box, line, replace, or clear. The only implied usage is placing a single block, with no exclusions or prerequisite context.

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