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

With no annotations, the description carries the full burden, and it usefully discloses cursor-based pagination and that concurrent edits require a fresh traversal for reconciliation. However, it omits whether this is a safe read, what is returned, or how an incomplete traversal should be interpreted.

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?

Two dense sentences with the core action front-loaded and no wasted filler. It is compact and functional, though the phrasing is terse enough to be ambiguous.

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 an 8-parameter tool with no annotations and no output schema, the description is thin: coordinate meanings, limit, return shape, and error behavior are all absent. Only the pagination loop is adequately covered.

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 0% across 8 parameters, so the schema does not document x, z, y, w, d, h, or limit. The description only clarifies 'cursor' and, implicitly, that x/z/w/d define a 'box', leaving most parameters unexplained.

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 action ('Page through exact cubes in x/z/y order'), which reads as a region-read operation distinguishing it from the single-cube get_cube sibling. It is clear on what it does, though it never explicitly names the sibling alternatives like get_overview or get_world_stats.

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?

It explains pagination mechanics ('Pass next_cursor as cursor with the same box until null') but never says when to choose this over get_cube, get_overview, or get_world_stats, nor any prerequisites for use. No when/when-not guidance or alternative routing is present.

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