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

Annotations only supply readOnlyHint and openWorldHint; the description adds real behavioral content beyond them: the paid-pass gating, the ranking factors, and concrete workability thresholds (under 2 mm rain, wind under 35 km/h). It does not mention rate limits or cost per call, but the added context is substantial.

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 sentence leads with the gating condition and then the ranking/output logic, with no filler sentences. It is dense with parentheticals but every clause carries information an agent needs.

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 carries the burden of describing results and does so: ranked spots plus a 3-day forecast with workable-day flags. Gating and thresholds are covered; only cross-tool routing to the other spot tools is missing.

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 coverage is 100%, so the schema already documents lat, lng, carrier, radius_km, and tz_offset_min in detail. The description references carrier-based ranking but adds no syntax, defaults, or format guidance beyond what the schema provides; baseline 3 applies.

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 specific action (ranks nearby spots) and the ranking criteria (carrier signal, Starlink open sky, flat ground) plus the weekly forecast overlay, which distinguishes it from generic siblings like find_spots or check_spot. It never explicitly names what it is not, so sibling differentiation rests on inference.

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 Camp Map Pass paywall implies the usage context (only when the user has a pass), but there is no explicit when-to-use versus find_spots, hunting_spots, or check_spot, and no stated exclusions or prerequisites beyond the subscription. Usage is implied rather than directed.

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