Read one block

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 behavioral disclosure, but it merely restates that a block state exists at a position. It does not confirm that this is a read-only operation, describe what the returned block state contains, or mention failure/error behavior. The only read-only signal comes from the name and title, not the description.

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 short sentence with no fluff, which is concise. However, it is closer to under-specification than to disciplined conciseness: it is a noun fragment rather than a structured instruction and omits key operational details.

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 tool with no annotations and no output schema, this description is incomplete. It does not explain the coordinate format for 'pos', the default or optional behavior of 'world', or what the block state result looks like. The description leaves too much for the agent to infer.

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?

Schema description coverage is only 50%, and the description adds little beyond the word 'position'. The required 'pos' parameter has no schema description and no format clarification in the description, while the optional 'world' parameter is left entirely unaddressed despite having a partial schema description. The description does not compensate for the undocumented parameter.

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 names a clear resource (block state) and a location (position), and the title 'Read one block' supplies the action. This distinguishes it from sibling tools like read_region and get_heightmap, which operate over areas. It is not a fully explicit verb phrase, but the intent is unambiguous.

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 gives no guidance about when to use this tool versus alternatives such as read_region, preview, or get_heightmap. It does not state exclusions, limitations, or recommended contexts. Usage can only be inferred from the tool name and title.

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