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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety and idempotency are covered structurally. The description adds real context beyond that: the geographic scope (states, provinces, countries) and the specific counts returned, which is what an agent needs to judge whether calling it is worthwhile. It does not restate the annotated safety traits, so no contradiction.

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, front-loaded with what the tool returns, followed by the concrete reason to call it. Every clause carries information; there is no filler or restatement of the title.

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 discovery tool with an output schema, the description supplies everything an agent needs: the scope of the result set, the fields returned, and the downstream tools that consume the returned `state` values. Nothing material 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?

The tool takes zero parameters, so there is no per-parameter semantics to explain and the baseline of 4 applies. The description does add meaning about the shape of the result (counts per region plus hub URL) even though the output schema already documents it.

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 resource (every state, province and country PeakCam covers) and enumerates exactly what it returns: resort, reporting, SNOTEL and cam counts plus the hub page URL. That granularity lets an agent distinguish it from sibling lookups like search_resorts or get_resort_profile without opening a schema.

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?

Gives an explicit trigger ('call it to learn the valid `state` values for find_powder, get_opening_dates and get_percent_of_normal') and a natural-language use case ('where does PeakCam have data'). It names the three dependent siblings by name, so the routing decision is unambiguous.

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