list_stations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't explain what the refresh parameter does behaviorally, whether results are cached, how many stations may be returned, or what the output structure looks like despite having an output schema. The description is thin on behavioral specifics for an un-decorated tool.

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?

Single sentence, zero waste, and front-loaded with the core action. Concise but arguably under-specified given the existence of a refresh parameter that warrants explanation.

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?

With an output schema present and a single self-named optional parameter, the tool is relatively simple. However, the refresh parameter's semantics are unexplained, and for a tool with no annotations, more detail on what 'standard NES-LTER stations' means (e.g., fixed set vs. dynamic) would help complete the picture.

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 carries full responsibility for the parameter. The refresh boolean is entirely undocumented in both the schema (beyond its name and default) and the description. However, there is only a single optional parameter with a self-explanatory name, so the gap is modest.

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 "List standard NES-LTER stations with coordinates and station metadata," which names a clear verb (list) and resource (stations) plus scoping (NES-LTER) and content (coordinates, metadata). It distills the tool from siblings like list_cruises/list_casts, but doesn't explicitly distinguish it from get_station_profile which is a related station-focused tool.

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 a listing/overview use case but provides no explicit guidance on when to use this vs. get_station_profile or other listed siblings. It does not mention the refresh parameter's role, which may be relevant to caching behavior. No when-not-to-use guidance is given.

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