get_elevation

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

The description explains the parameters and their formats but does not disclose behavioral traits such as rate limits, authentication requirements, or handling of invalid inputs. Without annotations, it partially meets transparency needs but lacks depth.

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 concise and well-structured, with a clear purpose statement followed by bulleted parameter descriptions. Every sentence adds value without redundancy.

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?

The description thoroughly covers parameter semantics but lacks information about return values (no output schema) and constraints (e.g., valid coordinate ranges, maximum coordinate count). This leaves gaps for an agent to use the tool correctly.

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?

With 0% schema description coverage, the description fully compensates by providing detailed explanations, examples, and types for each parameter (lon, lat, coordinates, relativeTo), adding significant meaning beyond the schema structure.

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 'Get elevation for locations on land or water,' using a specific verb and resource. It distinguishes itself from sibling tools like geocode or get_basemap_tile, which serve different purposes.

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 explicit guidance on when to use this tool versus alternatives. It does not specify conditions, prerequisites, or when not to use it, leaving the agent with only implicit context from sibling names.

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