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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds that the call requires authentication and that output is normalised to SI units with source provenance, but says nothing about pagination, rate limits, or result shape.

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 definition is short with no padding, and the identifying clause is front-loaded. However, the opening phrase "TerraMCP authenticated router: flood_list_warnings" redundantly restates the name rather than adding information.

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 two-parameter filtering tool (county, max_severity) with no output schema and no parameter descriptions, the definition should explain the filtering semantics and warning severity scale. Instead it leaves both parameters and the practical behaviour ambiguous.

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 description mentions neither parameter. The county filter and the max_severity integer (range 1-4, default 3) are completely undocumented anywhere, so the agent cannot know their intended semantics.

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 mostly restates the tool name ("flood_list_warnings") and adds generic boilerplate about returning "normalised SI data and source provenance." It never states what a warning entry is or how this differs from siblings like flood_find_stations or flood_get_readings. Only the name itself conveys the actual purpose.

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?

There is no when-to-use guidance, no prerequisite conditions, and no routing to alternatives such as flood_get_readings or flood_find_stations. The agent must infer usage purely from the tool name.

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