get_full_terrain_data

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

Discloses that the response is large and describes what is returned (full sr_dem grid, model info, shapes, per-cell grids). No annotations provided, so description carries full burden; it does not mention auth needs or potential costs, but is still informative.

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?

Concise paragraph followed by structured Args and Returns. No wasted words, front-loaded with purpose.

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?

Given 4 parameters and no output schema, the description covers purpose, parameters, return value, and usage guidance. No apparent gaps for an agent to understand invocation.

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 coverage is 0%, but the description fully documents all 4 parameters: latitude/longitude with ranges, bbox_size_m with range and default, metrics list with options and default. Adds complete semantic meaning.

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?

Clearly states the tool gets full super-resolved DEM and terrain metric grids for a location, and distinguishes itself from sibling 'analyze_terrain' by noting this tool is for detailed spatial analysis vs quick summaries.

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?

Provides clear context: recommends using analyze_terrain for quick summaries when large responses aren't needed. Does not explicitly state when not to use this tool, but the guidance is sufficient.

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