env_hazard_overview

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

Annotations indicate readOnly, idempotent, non-destructive. Description adds context: deterministic, network-free, and explains the background of API shutdown. No contradiction, but could mention side effects more explicitly.

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?

Description is front-loaded with purpose, includes background and notes. Slightly long but well-organized with tags. Minor redundancy in background section.

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 an overview/routing tool, the description fully covers what it returns (mapping of hazards to tools and platform links). Output schema exists, so return values are documented externally. Complete guidance for selection and usage.

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 for language is minimal but present. Description adds context that language is 'für die Portallinks'. Schema coverage is 0% per context, so description helps marginally; baseline 3 is appropriate.

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 provides an overview of Swiss natural hazards, mapping each hazard to a specific tool or official warning platform. It distinguishes from siblings by listing concrete tools like env_flood_warnings.

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?

Explicit usage guidance: use as entry point, for live data use linked tools. Includes when-not-to-use (aggregated weather warnings are for meteoswiss-mcp) and provides context with <use_case> and <important_notes>.

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