Collect Blocks (Mine + Pick Up)

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

Discloses that it is destructive (mines), involves movement (walks over), and may fail partway. Aligns with destructiveHint=true and adds error conditions not present in annotations. Could specify count behavior more precisely but overall strong.

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?

A compact paragraph covering action, contrast, return, and errors. Every sentence adds value; no filler.

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?

Covers main behavior, purpose, return type, and error modes. Minor gap: no explicit mention of how count affects behavior or what 'nearest' range is, but sufficient for a simple tool.

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?

The schema documents block_name with examples but count lacks any description. The tool description does not mention count at all, leaving its semantics (e.g., how many blocks to collect) to inference. This is a gap given 50% schema coverage.

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?

Clearly states it finds, mines, and picks up blocks, with a concrete example. Explicitly differentiates from minecraft_dig_block by noting it also collects drops.

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?

Gives a specific use-case ('when you actually want the item in inventory') and names the alternative tool. Includes an example query, making when-to-use obvious.

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