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 adds two useful behavioural facts: calls require authentication, and results are normalised to SI with source provenance attached. It says nothing about pagination, rate limits, or missing-data behaviour, so it is adequate but not rich.

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 text is very short and front-loaded, so it is not bloated, but the first clause ('TerraMCP authenticated router: nrfa_get_timeseries') is pure filler that repeats the name. Space saved is wasted on restatement rather than on the missing parameter and usage detail.

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 tool with four parameters, three of them required, an enum input, and no output schema, the description is far too thin. Only the return format (normalised SI plus provenance) is addressed; nothing about station/date semantics or the data_type choices is covered.

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 explains none of the four parameters. The required station_id, start, and end, and especially the data_type enum (gdf/ndf/cdr), are completely undocumented — an agent has no way to know which data type is appropriate without external knowledge.

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 largely restates the tool name ('nrfa_get_timeseries') and adds only that it returns 'normalised SI data and source provenance'. It never states the actual action in domain terms — retrieving a hydrological time series for a given NRFA station across a date range — so an agent cannot confidently distinguish it from siblings like ea_hydro_series, usgs_daily, or flood_get_readings.

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 statement of when another series tool is preferable, and no prerequisites beyond the word 'authenticated'. With 15 sibling tools covering overlapping hydrology/rainfall data, this omission forces the agent to guess.

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