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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds real context beyond that: it distinguishes live components (which carry an as-of time) from static ones and discloses the upstream sources (NPS alerts, NWS, AQI, satellite hotspots, etc.), which is meaningful behavioral detail.

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?

Front-loaded with the scope ('Right now at one park') and then a dense but purposeful enumeration of the data returned; nearly every clause conveys actionable coverage information. It runs long, but the length is justified rather than padding.

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 conveying return content, and it does so thoroughly — listing alerts, weather, air quality, fire, roads, campground/visitor-center schedules, webcams, sun/moon, and forecast per country. Nothing an agent needs to decide and call it 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 both parameters. The description restates that a park id or name is accepted with examples, but adds nothing about include_campgrounds or any format nuance beyond the schema, 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?

States a specific verb (get) and resource (park status) and goes further by enumerating exactly what 'status' aggregates for US vs Canadian parks. This cleanly separates it from siblings like themeparks_get_park_status and ski_get_resort_status, and pins down the single-park live scope with 'Right now at one park.'

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 phrase 'Right now at one park' implies this is for live current conditions at one location, which implicitly routes a park-level query here rather than to search tools. However, it never states when NOT to use it or names any alternative (e.g. nationalparks_search_parks for discovery), leaving the routing to inference.

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