get_timeseries

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

With no annotations, the description carries the full burden, and it does disclose read-only semantics plus two output traits (source provenance, missing-data caveats). It omits other operationally important behavior such as time-range limits, ordering, pagination, or permission requirements.

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?

A single front-loaded sentence that packs purpose, safety profile, and output caveats with zero filler. Every clause earns its place.

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 no annotations and no output schema, the description must carry more weight than it does. It covers the read-only nature and hints at return contents, but leaves range semantics (inclusive/exclusive bounds, maximum span) and response shape unspecified.

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 67%, with start_time and end_time thoroughly documented in the schema and type_codes left bare. The description adds semantic color by framing type_codes as 'metric types' and reinforcing the read-only observational nature, but contributes little beyond the structured fields.

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 states a specific verb ('Read-only ... observations') and resource ('time-series') scoped to 'selected metric types', which is a clear, non-tautological purpose. It does not, however, name or contrast with any sibling such as list_supported_timeseries_types or get_daily_summary, so an agent gets no explicit routing help.

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?

There is no explicit when-to-use/when-not guidance or named alternative. The clause 'no clinical interpretation' implies a boundary (raw observations vs. interpreted summaries), giving implied usage context only, which the agent must infer.

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