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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that alerts are 'real-time' and lists alert types, which provides some behavioral context. However, it does not elaborate on data freshness, update frequency, or response format beyond what annotations cover.

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?

The description is two sentences long and front-loads the key information: what the tool does (real-time alerts) and how to use it (filter by state or park code). No extraneous text.

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 simple read-only query tool with an output schema and comprehensive annotations, the description fully conveys the purpose and usage. It mentions the data source (NPS public domain) and alert types, making it complete for the given complexity.

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% with well-described parameters. The description only mentions filtering by state or park code, which aligns with schema but adds no new meaning. Other parameters (q, limit, start) are not referenced, so the description does not enhance semantics beyond the schema.

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 clearly states the tool returns 'real-time alerts (closures, hazards, fire, flood, danger) for US national parks' and offers filtering by state or park code. This distinguishes it from siblings like travel.nps.campgrounds, travel.nps.parks, and travel.nps.things_to_do.

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 description implies usage through the mention of filtering options but does not explicitly state when to use this tool versus alternatives like travel.nps.parks or travel.nps.campgrounds. No when-not-to-use scenarios or alternative comparisons are provided.

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