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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds value by specifying return contents (station IDs, names, coordinates) and the filter behavior (by type). It does not mention pagination or potential performance characteristics, but given the strong annotation coverage, the added details are sufficient.

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 description is a single, front-loaded sentence that communicates purpose, filtering, and return values with no wasted words. It is concise, efficient, and well structured for quick parsing by an agent.

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 simple listing tool with two optional parameters, complete schema descriptions, an output schema present, and strong annotations, the description fully covers the essential context: what the tool does, what it returns, and how to filter. No significant gaps remain; the output schema handles return structure details, so the description need not repeat them.

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 100%—both 'type' and 'format' have descriptions in the schema. The description repeats the filter options and says 'List all', which adds little beyond the schema. Since the schema fully documents the parameters, a baseline of 3 is appropriate; the description does not introduce new semantic details.

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 uses a specific verb ('List') and resource ('NOAA Tides & Currents monitoring stations'), and clearly distinguishes from siblings like currents, water_level, and station_metadata by focusing on station discovery. It also names the filter types (waterlevels, currents, physical, meteorological) and return content (IDs, names, coordinates), making the tool's role unmistakable.

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 usage as a discovery tool ('List all stations; filter by type') and mentions 'Returns station IDs, names, and geographic coordinates', which suggests a precursor to data-retrieval tools. However, it does not explicitly mention alternatives or when to prefer station_metadata or current/water-level tools. No exclusions or when-not-to-use guidance is provided.

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