Place Block

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

Beyond annotations (mutation, not idempotent), the description discloses auto-walking, the requirement for a solid neighbor, and the empty-space prerequisite. It also lists specific errors, adding transparency about limitations and failure modes.

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 thorough yet concise, with each sentence providing meaningful detail (behavior, constraints, returns, errors). Structure is front-loaded with the core action and followed by necessary conditions and expected outcomes.

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 4 parameters and no output schema, the description covers the essential behavioral contract, constraints, and error cases. It doesn't mention nuances like block orientation, but given the simplicity of the tool, the description is sufficiently complete.

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 low (only block_name described). The description only mentions 'world coordinates' without clarifying the coordinate system or format for x, y, z. It does not compensate adequately for the missing schema descriptions of these parameters.

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 tool places one block from inventory at given world coordinates, distinguishing it from sibling tools like minecraft_build_structure. The specific behavior of auto-walking and finding a solid neighbor further clarifies its unique purpose.

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?

Provides clear context for when this tool is appropriate: placing a single block at an empty, solid-adjacent location. It also implies you don't need to be in position due to auto-walking, but it doesn't explicitly contrast with alternatives like build_structure or place multiple blocks.

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