get_dataset_variable_data

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

With no annotations, the description must disclose behavioral traits. It only notes that 'Time is always included in the results,' but omits other critical aspects such as data ordering, pagination, limits, or whether the tool supports subsetting beyond time range. The lack of safety or mutation hints is a gap.

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 concise at one sentence, but it lacks structure and omits essential details. While brevity is positive, the trade-off is missing critical information that would make it more useful.

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?

Given 6 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the return format, data types, error conditions, or how parameters interact. The agent cannot form a complete mental model of the tool's behavior.

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 description adds no meaning to the 6 parameters, despite 0% schema coverage. It does not explain the purpose of erddap_url, dataset_id, variable_name, start_time, end_time, or exclude_nans. The agent must rely on parameter names alone, which may be insufficient.

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 clearly states the tool retrieves data for a variable from an ERDDAP dataset, using a specific verb ('Get') and resource ('data for a variable'). This distinguishes it from sibling tools that focus on metadata (list_datasets, list_dataset_variables) or search (search_datasets), making it obvious when to use this tool for actual data retrieval.

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 alternatives. For example, it does not explain that this tool is for fetching observations while list_dataset_variables is for discovering variable names. The agent must infer usage from the name and description alone.

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