find_blocks

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 disclosing behavioral traits. It does not state whether the operation is read-only, what it returns, or any side effects. 'Find' implies a search operation, but the description omits critical details like return format or potential limitations.

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 is front-loaded with the main action and resource. Every word earns its place, with no redundant information.

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 simple find-tool with a well-described schema, the description is adequate but has gaps. No output schema means the description could have mentioned return values (e.g., positions), and it doesn't address behavioral nuances like whether the search respects line-of-sight or is limited to loaded chunks. It's functional but not comprehensive.

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?

All three parameters are fully described in the input schema, so the baseline is 3. The description adds minimal semantic value beyond the schema, only hinting at 'specific type' and 'near the bot' which correspond to blockName and maxDistance. It does not enrich the parameter meanings further.

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 finds blocks of a specific type near the bot, using a specific verb and resource. It distinguishes itself from sibling tools like get_block_info (which inspects a block), dig_block/collect_block (which break blocks), and place_block (which places blocks).

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 the usage context (searching for blocks near the bot) but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions. It's clear enough for typical use, but lacks the explicit alternative naming seen in higher-quality descriptions.

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