signal_timeseries

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

Beyond annotations (readOnly, idempotent), it adds key behavioral details: the series is bounded, evenly downsampled, and max_points is capped at 2,000. This gives practical constraints not present in 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?

A single, concise sentence that front-loads the core purpose and key constraint. 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?

Given the output schema exists and annotations are strong, the description covers critical constraints (downsampling, max_points cap) but does not explicitly state the role of time bounds or other parameters. Still, it is adequate for the tool's complexity.

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?

The description only adds semantics for max_points (capped at 2,000), but schema coverage is 0%. Parameter names like dbc_path, log_path, message, signal are self-explanatory, yet the description does not explain their roles or time_start/time_end semantics, leaving a gap.

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?

Clearly states it returns a bounded, evenly downsampled [timestamp, value] series for one DBC signal, distinguishing it from sibling tools by its focus on a single signal's time series.

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?

Implies usage for extracting a downsampled time series of one signal, but does not explicitly mention when to use this instead of siblings like decode_frame or read_frames. Provides context without direct exclusions.

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