Query time series

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

Discloses important behaviors: response cap at 500 rows with pagination via offset, silent coarsening of Hour aggregation, and refusal of None aggregation without allowRaw. Consistent with readOnlyHint and openWorldHint annotations.

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?

Extremely concise: three sentences pack purpose, aggregation guidelines, and pagination detail. Front-loaded purpose with clear, scannable structure. No wasted words.

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?

Covers all key aspects: date range, aggregation options, row limit, and pagination. Lacks explicit output schema description, but given openWorldHint and focus on input constraints, it is sufficiently complete for its use case.

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 100% so baseline is 3. The description adds value by explaining aggregation behavior and allowRaw necessity, beyond the schema's enum descriptions. Does not repeat schema info unnecessarily.

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 it queries time series data for a node between dates, answering 'how much / what pattern over time'. It distinguishes from sibling tools like get_latest or list_sources.

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?

Provides detailed guidance on aggregation levels (Day, Hour, None) and conditions (Hour coarsens beyond 32 days, None requires allowRaw for >7 days). Lacks explicit comparison to sibling tools but offers practical usage advice.

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