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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds substantial context beyond that: status reports subsystem availability and replication lag, elevation returns surface and raw model heights, metrics report rates/latencies/dataset ages, and the public-vs-subscription-key auth requirement is disclosed. This is genuinely useful behavioral detail not available in the structured fields.

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?

Four sentences, front-loaded with the operation list followed by per-operation output detail and the auth constraint. Each sentence carries information, though the output-detail sentence could be trimmed and the structure does not group constraints as cleanly as it could.

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?

With no output schema, the description does describe what several operations return (subsystem availability, replication lag, surface/raw model heights, request rates, latency percentiles, dataset ages) and covers the auth requirement, which is enough for a dispatcher tool. The notable gap is sibling differentiation against basemap_catalog/elevation/service_status, plus no disclosure of defaulting behavior for zoom/bands/window (left to the schema).

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 every parameter (lat, lon, zoom, bands, window, operation) is already documented with type bounds and per-operation applicability in the schema. The description reinforces operation-level semantics but adds no new parameter detail, so the baseline 3 for high coverage 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 uses a concrete verb (Read) and enumerates the six resources it covers (service status, basemap catalog, point elevation, contours, usage, metrics), giving a clear picture of the tool's scope. However, it draws no distinction from siblings like basemap_catalog, elevation, and service_status, which appear to overlap heavily with the 'basemaps', 'elevation', and 'status' operations, leaving the agent unable to tell which tool owns that functionality.

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?

There is no explicit when-to-use guidance, no statement of when a sibling should be preferred, and no conditions selecting among the six operations beyond the auth note. The auth sentence ('Status and basemaps are public; other operations require a subscription key') is a prerequisite but not routing guidance.

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