get_map_series_data

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read or write operation, what permissions might be required, whether it has rate limits, what format the data returns in, or any error conditions. The description provides zero behavioral context beyond the minimal name restatement.

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?

While technically concise with just 'geofred/series/data', this represents under-specification rather than effective brevity. The single phrase doesn't provide enough information to be useful, and there's no structure or front-loading of critical information. The description is too minimal to serve its purpose.

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 the tool has 3 parameters with 0% schema coverage, no annotations, but does have an output schema, the description is severely inadequate. While the output schema may document return values, the description fails to explain what the tool does, when to use it, how parameters work, or any behavioral characteristics. For a data retrieval tool in a complex API with many alternatives, this description provides insufficient context.

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?

With 0% schema description coverage and 3 parameters (series_id, date, start_date), the description provides no information about any parameters. It doesn't explain what a 'series_id' represents, what format dates should use, how date and start_date interact, or what happens when parameters are omitted. The description fails to compensate for the complete lack of schema documentation.

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 'geofred/series/data' is essentially a tautology that restates the tool name with minimal additional information. It vaguely suggests retrieving data related to a series in the GeoFRED context, but doesn't specify what kind of data, for what purpose, or how it differs from similar tools like 'get_series_observations' or 'get_map_regional_data'. The description lacks a clear verb and specific resource definition.

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 provides absolutely no guidance on when to use this tool versus alternatives. With numerous sibling tools available (including 'get_series_observations', 'get_map_regional_data', and 'get_series'), there's no indication of what distinguishes this tool's functionality or appropriate use cases. The description fails to mention any prerequisites, constraints, or relationships to other tools.

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