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

With no annotations, the description carries the full burden and does add valuable behavioral context: 'Requires Pro key' alerts to access restrictions, 'Returns a URL' explains the output mechanism, and 'Supports PNG / SVG / PDF' discloses format flexibility. It also mentions 'three neighbourhood window sizes,' which hints at the chart's internal structure. It does not contradict any annotations.

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 compact and front-loaded, using two sentences to convey the tool's core function, return value, access requirement, and supported formats. Every sentence earns its place with no redundancy or fluff.

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 the tool's moderate complexity, the description is reasonably complete: it covers purpose, return type, access prerequisite, and output formats. Since an output schema exists, the return values are already structured, and the description appropriately supplements with non-schema information. It could mention error conditions or more chart details, but it is not a significant gap.

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 100%, and the schema already documents all four parameters (lat, lon, dataset_id, fmt) with clear descriptions. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 the tool's function: 'Generate a range-box chart showing terrain slope Min/Avg/Max across three neighbourhood window sizes.' It specifies the resource (terrain slope), the chart type (range-box), and the return type (URL to chart image). This distinguishes it from sibling tools like LP_Get_Slope_Stats, which likely return raw statistics.

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 does not explicitly state when to use this tool vs alternatives, such as LP_Get_Elevation_Chart or LP_Get_Terrain_Map. It only states what it does, leaving the agent to infer usage from the name and sibling context. No exclusions or alternative recommendations are provided.

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