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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds two useful bits of context beyond that — that the call costs nothing ('Free.') and that a payment path (x402) is described rather than executed — but says nothing about output format or size, keeping it at a solid middle score.

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 lists the covered topics efficiently, with the cost note isolated as 'Free.' The list runs on somewhat without connectives, but every clause carries distinct information and nothing is wasted.

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 zero-parameter, read-only info tool with annotations supplying the safety profile and no output schema to explain, the description covers content, pricing, payment method, and purchase path. It is nearly complete, only missing a note that no map artifacts are produced or returned.

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 has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the description misleads about inputs.

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 enumerates the specific informational payload (map contents, price, imagery coverage/quality, x402 payment, direct purchase), which makes it clear this is a read-only 'about the service' endpoint rather than an action tool. It lacks an explicit verb ('returns'/'describes') and never contrasts itself with the sibling action tools, so it stops short of a 5.

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 statement of when to call this versus check_map/make_map/preview_map/revise_map, nor any prerequisite or sequencing guidance. The trailing 'Free.' hints there is no cost barrier but does not constitute usage guidance.

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