get-block-info

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. The phrase 'Get information' clearly implies a read-only operation, but the description does not describe what information is returned (e.g., block type, properties), nor any potential errors such as out-of-bounds coordinates. It adds only the most basic transparency.

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, clear, and front-loaded sentence. Every word contributes to conveying the tool's purpose; there is 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?

This simple tool has no output schema and no annotations, so the description should explain what kind of information is returned and possibly distinguish it from siblings. It does neither, leaving the return value vague and the usage context unclear. The lack of any guidance on when to use this instead of 'get-blocks-info' is a notable gap.

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 already provides 100% coverage for the three parameters, each described as a coordinate. The description's phrase 'at the specified position' merely reinforces the schema's meaning without adding details about coordinate format, bounds, or how they are interpreted.

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 with a specific verb ('Get information') and resource ('a block'), and scopes it to 'the specified position'. This distinguishes it from the sibling 'get-blocks-info' (plural) and 'get-nearby-block-types' to some degree, but it does not explicitly name alternatives.

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 provides no guidance on when to use this tool versus the many sibling tools like 'get-blocks-info' or 'get-nearby-block-types'. There is no mention of prerequisites, limitations, or context in which this tool is preferred.

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