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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. With no output schema, the description usefully discloses the return fields (bounding boxes, data build time, offline packs), which is exactly the behavioral context an agent cannot get from structured fields here; it still omits pagination, result size, and whether the list is filterable.

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?

A single front-loaded sentence identifies the resource first, then the returned attributes. There is no filler, hedging, or repetition of the title, and every clause carries information.

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?

For a parameterless, read-only listing tool with no output schema and no nested objects, the description supplies the essential return-value information an agent needs to decide whether calling it is worthwhile. It falls short of full completeness only because it says nothing about result volume or stability of the data.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument, list-everything call.

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?

States a clear resource (the provinces, territories and states the Camp Map covers) and enumerates what comes back with it, so an agent knows this is a static coverage listing rather than a lookup for a specific place. It does not explicitly distinguish itself from siblings like find_spots or check_spot, but the resource is specific enough that confusion is unlikely.

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?

Usage is only implied: the agent can infer this is the tool to call when it needs the map's coverage list, bounding boxes, build dates, or offline pack availability. There is no explicit when-to-use statement, no prerequisites, and no named alternative for related needs such as checking a specific spot.

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