list_dataset_rows

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

No annotations are provided, so the description carries full burden for behavioral disclosure, yet it says nothing about return behavior, pagination semantics (though limit/offset exist in schema), whether refresh has side effects, or how filtering interacts across the enumerated dataset types. The description fails to explain post-filter behavior, ordering, or error conditions.

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 efficient sentence with zero waste. However, it is under-specified rather than genuinely concise — brevity here trades away necessary usage detail for a complex 9-parameter tool.

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?

An output schema exists, which relieves pressure on describing return values, but this is a complex tool with nine parameters, 0% schema coverage, no annotations, and a list of dataset types whose filtering behavior is unexplained. The description is far too thin to enable correct invocation across the described dataset categories.

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 0%, so the description must compensate for nine parameters, but it mentions only 'fetch and filter' with no parameter specifics. It does not clarify what values 'dataset' accepts, the meaning of variable vs station vs time filters, how limit/offset paginate, or the purpose of the refresh flag. This is inadequate for nine parameters.

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 the tool fetches and filters oceanographic dataset rows (underway, bottles, nutrients, HPLC, chlorophyll, event), giving a clear verb+resource. However, it does not distinguish this from siblings like get_cast_profile or query_ctd, and 'list_dataset_rows' vs the many dataset-specific query tools creates ambiguity about which dataset types map to which filters.

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?

No guidance is provided on when to use this tool versus the many siblings (get_cast_profile, query_ctd, get_station_profile, get_dataset_schema). The description names dataset types but offers no selection criteria, prerequisites, or exclusions relative to the nine sibling tools.

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