get_timeline

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

No annotations are provided, so the description carries the full burden. It does describe the composite output (frames + event lines) and the data sources, but it says nothing about permissions, window limits beyond the schema's 1-60 range, whether the call is read-only, or how large the returned payload might be.

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?

Two sentences, zero filler, and the resource description is front-loaded before the usage guidance. 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 output schema, the description must convey return content, and it does so at a high level (contact sheet plus timestamp-aligned event lines). For a three-parameter, all-optional tool this is largely sufficient, though more on output shape/size would help.

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 schema already documents camera, last_seconds, and include_events. The description hints at the relationship between buffered history frames and last_seconds, and event lines and include_events, but adds no format or syntax detail beyond the schema baseline.

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?

States a specific verb (Returns) and a concrete composite resource: a contact sheet of buffered history frames plus timestamp-aligned event lines from serial/log adapters. This is distinguishable from siblings like capture_image or read_events, though it does not explicitly name those alternatives to sharpen the boundary.

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 second sentence gives a clear use case (correlating hardware events such as crash, reset, or button press with visual frames), which tells the agent when this tool is appropriate. It stops short of stating when NOT to use it or naming the sibling tools that would be used instead.

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