minecraft_collect

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

No annotations are provided, so the description carries the full burden of explaining behavioral impact. It does disclose that the tool digs, implying world modification, but it does not explain inventory effects, what happens when no matching block is found, whether the tool can break blocks beyond reach, or any confirmation/failure behavior.

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 a single front-loaded sentence with no filler. It immediately communicates the action and object, and every word carries meaning.

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 three parameters, no annotations, no output schema, and no schema property descriptions, this definition is too thin. An agent would still be uncertain about how count and maxDistance interact, what errors occur, and how this differs from minecraft_dig.

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%, so the description must compensate for undocumented parameters. It loosely maps 'block name' to the block parameter and 'nearby'/'one or more' to maxDistance and count, but it does not define units, valid name formats, or how count behaves when fewer blocks exist.

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 uses a specific verb ('Find and dig') and a concrete resource ('nearby blocks by block name'), making the tool's core action clear. It is distinguishable from generic siblings like minecraft_dig because it emphasizes finding blocks by name and collecting one or more, but it does not explicitly contrast itself with those siblings.

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 explicit guidance about when to use this tool versus alternatives such as minecraft_dig, minecraft_goto, or minecraft_look. The phrase 'nearby blocks by block name' implies a use case, but the description never states prerequisites, exclusions, or how to choose between this and related tools.

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