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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and open-data scope are covered; the description usefully reinforces that data comes from a NOAA station and is predictive rather than measured. It says nothing about station ID requirements, coverage limits, or what happens when a station lacks predictions for the requested date.

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?

A single short sentence with no filler, and the key scoping information (day, NOAA station, predicted high/low) is front-loaded. Its terseness is efficient, though the noun-phrase phrasing omits an explicit action verb.

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 read-only lookup this is close to adequate, and no output schema exists so return-format detail is optional. However, with no output schema the description could at least hint that the result is a list of high/low events with times and heights, and the undocumented required station parameter is a real gap.

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 only 50%: the date parameter is well documented (YYYY-MM-DD UTC, default today) in the schema, but station — the sole required parameter — has no description anywhere. The description does not compensate by explaining the NOAA station identifier format or how to obtain one (e.g., via sensors_stations_near).

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 names a specific resource and output (predicted high and low tides) scoped to one day at a NOAA tide station, so an agent can tell it produces tide predictions rather than observations. It does not explicitly distinguish itself from the sibling sensors_tides, leaving the boundary between prediction and observed/harmonic tide data implicit.

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 prerequisites, and no mention of an alternative tool. An agent must infer from the word 'Predicted' alone whether to pick this over sensors_tides or sensors_water_gauge.

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