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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds the useful fact that all arguments are optional with a default limit of 20, but says nothing about result freshness, pagination, or what happens when filters match nothing.

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, purpose first, parameters second, zero filler. The dense argument clause is justified because the schema supplies no descriptions of its own.

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?

An output schema exists, so return values need not be explained, and all four optional parameters are covered in the description. The only real gap is routing guidance against the nearby advisory and conflict tools, which is a usage-guideline concern rather than missing call mechanics.

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 description coverage is 0% and the schema contains no enums, so the description carries the full burden — and it does: country as ISO alpha-3, the four severity values Low|Medium|High|Critical, days as a lookback window, and limit bounded 1-100 with default 20. Every parameter is documented beyond what the bare schema provides.

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?

Names a specific resource and scope: 'Active natural-disaster and severe-weather alerts', with examples (earthquakes, storms, floods, wildfires) that pin down the domain. An agent can distinguish it from aircraft/flight tools, but there is no explicit differentiation from the closest siblings, travel_advisories and conflict_events.

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 states what the tool returns but never says when to reach for it over travel_advisories or conflict_events, nor any prerequisites or exclusions. Usage must be inferred from the topic alone.

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