fetch_pds_data

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

The description mentions writing a file as a side effect but fails to elaborate on file location, overwrite behavior, or authorization requirements. With no annotations, the description carries the full burden but provides minimal behavioral disclosure.

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 very short (one sentence) but lacks structure. It is concise but omits essential details that could be presented in a more organized manner.

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 6 parameters (5 required), no schema descriptions, and no output schema content (though flagged as present), the description fails to provide adequate context. The return value is vaguely described as 'metadata/stats only' without structure, and no explanation of PDS PPI or data source is given.

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 coverage is 0%, and the description does not explain any parameters. Critical fields like dataset_id, parameters, start, stop, output_dir, and format remain undocumented, leaving the agent without guidance on how to fill them.

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 fetches timeseries data, writes a file, and returns metadata/stats. This specific verb+resource combination distinguishes it from sibling tools like browse_* or fetch_data.

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 on when to use this tool versus alternatives (e.g., fetch_data, search_spedas_data_sources). The description does not provide context for tool selection.

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