Get Real-Time Water Levels

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

Description adds value beyond annotations by noting the 6-minute update frequency and inclusion of quality flags. Annotations already indicate read-only and idempotent behavior; the description enriches this with operational details.

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 efficiently front-load the purpose and key details (update frequency, coverage, output). Every sentence adds essential information with no redundancy.

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?

The description covers purpose, output type, update cadence, and geographic scope. Missing details like output schema are compensated by its existence. Minor gap: no explanation of quality flags, but overall sufficient for a read-only tool.

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 100% with descriptions for all parameters. The description mentions 'feet or meters' which is already in the units enum, adding no new semantic meaning. Baseline 3 is appropriate as schema carries the load.

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 it retrieves real-time observed water levels from a NOAA station, specifying the type of data (latest or recent history) and geographic scope. However, it could better distinguish from the sibling 'tides.noaa.predictions' by explicitly noting it provides observed data versus predictions.

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 implies use for real-time or recent water level data but lacks explicit guidance on when not to use or alternatives like 'tides.noaa.predictions' for forecast data. Usage context is implied but not explicit.

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