get_timeline

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It does add useful context by explaining that the timeline shows chronological progression of detection events (e.g., object entered zone, attribute changes). However, it does not explicitly state read-only behavior, permissions, or output format, though the latter is covered by the output schema.

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 concise, consisting of two sentences with the action front-loaded. It provides a brief, relevant explanation of the timeline content without any unnecessary 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?

The description gives the core purpose and what the timeline contains, and the output schema covers return values. However, given the large sibling list, it lacks context on how this tool relates to other event/timeline tools and does not clarify differences from get_timeline_hourly.

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% with each parameter (limit, camera, source_id) having a descriptive comment. The tool description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 the tool's purpose: 'Get the detection timeline' with a specific verb and resource, and explains the timeline's content. However, it does not explicitly distinguish this from sibling tools like get_timeline_hourly or other event access tools, so it lacks sibling differentiation.

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 description provides no guidance on when to use this tool versus alternatives such as get_events, search_events, or get_timeline_hourly. It only describes what the tool does, with no context on selection criteria or exclusions.

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