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

No annotations are provided, so the description carries the full burden. It discloses two important behavioral traits: a Pro key is required, and all layers are reprojected to EPSG:3857 to avoid overlay mismatch. However, it does not mention rate limits, failure modes, or behavior when the Pro key is absent. For a read-only map generator, this is moderate transparency.

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?

Two sentences: the first lists the map components, the second adds projection and licensing constraints. Every word 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?

The description covers purpose, key components, projection consistency, licensing requirement, and supported output format. With an output schema present, return values need no explanation. It is complete for a map-generation tool, though it could mention use cases or limitations.

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 schema covers 100% of the 6 parameters with clear descriptions (lat/lon in decimal degrees, offset half-window, n_arrows grid density, dataset_id, fmt). The description adds no parameter-level detail beyond what the schema already provides, so the baseline score 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 opens with 'Generate a composite terrain map' and enumerates the specific layers (Google Hybrid satellite, smoothed contours with labels, flow-direction arrows, location pin). This clearly articulates the tool's function and distinguishes it from sibling tools like LP_Get_Terrain_3D and elevation/slope chart tools.

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 usage—you would invoke this when you need a composite terrain map—but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or refer to sibling tools. No guidance is given about choosing between map, 3D, or chart variants.

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