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

With no annotations, the description carries the disclosure burden. It adds useful behavioral context: the output is a Plotly go.Surface, colored by elevation, with a red spike pin for the query location, and supports PNG/HTML. It also states the Pro key requirement. This is sufficient for a read-only map tool, though it does not mention potential side effects (none expected) or rate limits.

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, front-loaded sentence that conveys the core purpose and key details (Plotly go.Surface, elevation coloring, red spike pin, Pro key, PNG/HTML). No wasted words.

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 covers the essential purpose, output type, formats, and access requirement. With an output schema present, return-value details are not needed. The tool is simple and the schema covers parameter constraints, so this is adequately complete for an agent to select and call it 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?

Schema coverage is 100%, so the baseline is 3. The description adds a small amount of semantic context (e.g., the red spike pin marks the query location, connecting lat/lon to behavior), but it does not explain parameter constraints or formats beyond the schema. Thus, it meets the baseline without adding substantial value.

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 'Generate a 3-D perspective terrain surface map' with specific output details (Plotly go.Surface, colored by elevation, red spike pin). This distinguishes it from sibling tools like LP_Get_Terrain_Map (likely 2D) and LP_Get_Elevation_Chart (profile chart).

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 implies when to use this tool—when a 3D perspective terrain surface is needed—and notes the Pro key requirement. While it does not explicitly name alternatives or exclusions, the 3D-specific language and sibling context provide clear guidance.

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