get-nearby-block-types

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

With no annotations, the description must disclose behavior. It accurately describes the read-only nature and the return data (counts and closest distance), but lacks details on the exact area bounds, potential costs, or edge cases.

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 single, focused sentence that immediately conveys the tool's action and output. No redundant words.

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?

The tool is relatively simple, and the description covers the core output, but without an output schema or parameter guidance, the agent must infer the exact response structure. The 'nearby area' is also ambiguous without distance context.

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 description does not explain the purpose of individual parameters, and the schema itself leaves maxDistanceUpDown undocumented. While it contextualizes 'nearby area', it fails to compensate for the missing parameter description.

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: retrieving unique block types and entity types in the nearby area, along with counts and closest distance. This distinguishes it from sibling tools like get-block-info and find-blocks-by-type, which focus on specific blocks or types.

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 tool is for surveying the nearby environment but does not explicitly state when to use it over alternatives like get-blocks-info or show-adjacent-blocks. No exclusions or alternative guidance is provided.

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