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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds concrete behavioral context: it is NOAA's own archive, hourly back to the 1970s for long-lived stations, which helps agents understand data granularity and historical depth. No contradiction with annotations.

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 with zero filler. The core function is front-loaded, followed by the authority statement and the usage preference. Every sentence earns its place.

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?

No output schema exists, but the description plus the detailed input schema (with examples) adequately cover how to call the tool. The description adds context about the data source and time range, which is essential for an agent to judge relevance. It does not explain return format or pagination, but the limit parameter addresses that. Overall, complete enough for correct invocation.

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% and each parameter is well-documented (e.g., dataset_id example, constraints with quoting rules, variables list). The description only adds general context about the data content (buoy/station timeseries) but does not explain individual parameters beyond what the schema already provides. Baseline 3 is appropriate.

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 ('Rows from a CoastWatch tabledap dataset') and a clear resource (buoy and station timeseries), and distinguishes itself from web search and implicitly from the griddap sibling. The use of 'AUTHORITATIVE' and specific examples of data fields (water temperature, wind speed) makes its purpose 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 explicitly says to prefer this over web search for buoy observations, and clarifies it is for buoy/station timeseries. It does not explicitly mention the griddap sibling as an alternative, but the context provided (tabledap vs griddap) is implied by the name and the description of the data type. This is clear enough for guiding selection.

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