show-adjacent-blocks

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

Since no annotations are provided, the description carries the full transparency burden. It explains the exact spatial coverage (horizontal directions and height levels) and the bot's 2-block height, which adds significant behavioral context. The verb 'show' implies a read-only operation, though return format and side effects are not explicitly stated.

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 concise: two sentences, with the core purpose in the first sentence and additional context in the second. It is front-loaded and contains no unnecessary 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?

While the description defines the scope of blocks shown, it does not mention what information is returned for each block (e.g., type, position, visual representation). With no output schema, this is a notable gap, though the tool's simplicity and clear purpose make it usable as-is.

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?

This tool has zero parameters, so the baseline score is 4. The description appropriately adds no parameter-specific details, as none exist; the schema alone is sufficient.

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 states a specific verb ('Show') and resource ('all blocks directly adjacent to the bot'), with explicit details on horizontal directions and height levels. This clearly distinguishes it from sibling tools like get-nearby-block-types or get-block-info, which have different scopes.

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 phrase 'Good first call when stuck' provides explicit usage guidance, making it clear when to use this tool. While it does not name alternative tools or exclusions, this contextual hint is sufficient for a simple reconnaissance tool.

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