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

With annotations already covering read-only, idempotent, non-destructive behavior, the description adds meaningful context: the records are historical, observation times may predate archive download, advisory status is absent, and source/freshness metadata is returned. It does not describe pagination behavior or query-search behavior, but the key staleness and interpretation caveats are disclosed.

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 compact and front-loaded with the tool purpose before adding historical-data caveats and units. Every sentence contributes useful interpretation or scope information without unnecessary repetition.

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 the historical nature, units, direction convention, and freshness metadata, which are important for interpreting this archive-backed tool. However, with no output schema and a nested input object lacking field descriptions, it is incomplete on query filters and pagination semantics.

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?

The input schema has 0% parameter description coverage and contains nested query fields for q, limit, offset, region, and category. The description only indirectly maps to the category values via 'station, access and port' and does not explain q, region, limit, offset, or how the nested query object should be used.

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 states a specific verb and resource: browsing dated California station, access, and port source records from a packaged archive. It clearly distinguishes the tool as historical source-data browsing rather than live condition reporting, though it does not explicitly contrast itself with similarly named California list tools.

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 gives implied usage constraints by saying this is historical source data, not continuous live conditions, and carries no current beach-advisory status. However, it does not explicitly say when to choose this tool over alternatives such as list_california_facilities, list_california_spots, or current-condition tools.

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