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

With no annotations provided, the description carries the full behavioral burden. It does disclose the core behavior — returning occupied cells as [index,type,height] plus a preview — which is the main trait of a read tool, but it never explicitly states that the operation is read-only with no side effects, relying instead on the 'get_' prefix to imply it.

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 sentence front-loads the resource and packs two pieces of information — the data format and the ASCII preview — with zero redundancy. Nothing repeats the name or title, and every word earns its place.

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 parameterless read tool with no output schema, the description covers what an agent needs to invoke it (no inputs) and what to expect back (cell triples plus a preview). Minor ambiguity remains about the meaning of 'index', 'type', and 'height', but this is acceptable given the tool has no inputs and no schema exists to elaborate.

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 has zero parameters with trivially 100% coverage, so the baseline of 4 applies — there is nothing to document. The description instead clarifies the output payload, which is the only semantic content an agent needs for this tool.

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 specific resource ('coarse top-surface raster') and specifies the exact return shape ('[index,type,height]' plus an ASCII preview), so an agent knows precisely what this tool produces. It is clearly a read-oriented overview distinct in content from sibling getters like get_cube, get_region, and get_world_stats, though it never explicitly draws that contrast.

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?

No guidance is given on when to choose get_overview over the sibling getters, and no alternatives or exclusions are mentioned. An agent must infer the intended use case purely from the name and title, which is insufficient for routing.

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