Get Time Series

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

With `readOnlyHint: true` already covering the safety profile, the description adds useful operational context: result timestamps include time zones and the agent should translate them to the user's local time zone when known. It also discloses the data-type eligibility constraint. It does not discuss pagination or response shape, but an output schema exists.

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 three tight sentences with no filler. It front-loads the core action, then the eligibility and alternative tool, then the time-zone handling note.

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?

For a read-only query tool with full parameter descriptions and an output schema, the description covers the critical non-schema context: supported data types, the fallback to `get_records`, and time-zone handling. Nothing essential for correct invocation appears to be missing.

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 100%, so the input schema already documents all seven parameters, including defaults, accepted calculation names, and time-zone requirements. The description only reinforces that `data_type` comes from `get_data_catalog` and that timestamps carry time zones; it adds little parameter syntax beyond the schema.

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 uses a specific verb and resource: "Get calculated per-interval time-series values for a single data type." It distinguishes this tool from the sibling `get_records` by explaining which data types are supported and where unsupported types should be read instead.

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?

It explicitly states the eligibility condition: only data types that `get_data_catalog` lists as usable with this tool are supported, and other types can be read with `get_records`. This gives clear when-not and alternative guidance, though it does not compare against other series-specific siblings such as `get_location_time_series` or `get_sleep`.

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