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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuinely non-structured context: the weather source is the National Weather Service's latest observation and alerts, and the data is current conditions rather than a forecast, which prevents a common misuse.

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 with zero filler: the trigger condition comes first, and the data-source/currency clarification follows. Every clause earns its place.

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 single-parameter, read-only tool with no output schema, the definition covers the trigger, the data source, and the currency semantics. It leaves the response shape implicit (what exact weather fields and alert structure come back), but nothing essential to calling it correctly 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%, and the park_id field already documents accepted keys, canonical IDs, names, and shorthands in detail. The description adds only the constraint of 'one supported park', which is marginal beyond what the schema provides, so the 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?

The description states a concrete resource set: weather, storms, heat, lightning, weather alerts, and the count of downed rides at one park. That is specific enough to distinguish it from siblings like parky_get_waits or parky_get_crowd_actuals, but it never names a sibling, so an agent must infer that parky_get_ride_outages handles per-ride outage detail.

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 opening clause 'Use this when a visitor asks about...' gives an explicit, concrete trigger list, including the 'right now' temporal constraint. It stops short of stating when NOT to use it or naming the alternative tool for forecasts and per-ride outage history.

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