collect_block

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'Navigate to and collect', with no mention of whether the block is destroyed, if tools are required, what happens if the block is unreachable, or how collected items are handled. This is a significant transparency gap for a tool that likely has complex side effects.

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, concise sentence that directly conveys the essential purpose. Every word contributes meaning with no redundancy or filler, making it highly efficient.

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?

Given the lack of output schema and annotations, this description is under-specified for a tool that involves navigation and collection. It does not explain return behavior, failure handling, or prerequisites, leaving the agent with an incomplete picture of how to use the tool successfully in a complex environment.

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 input schema fully documents both parameters (blockName and count) with clear descriptions, so schema coverage is 100%. The tool description adds no additional parameter semantics, but the baseline of 3 is appropriate since the schema already provides the necessary meaning.

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's function: 'Navigate to and collect a specific block type'. This includes a specific verb ('collect') and resource ('block type'), and the 'Navigate to' aspect distinguishes it from sibling tools like 'dig_block' or 'find_blocks', which focus on digging or finding without movement.

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?

The description implies when to use this tool: when you want to collect a specific block by navigating to it. However, it does not explicitly state when not to use it or mention alternative tools, leaving the usage context somewhat implicit rather than clearly delineated.

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