list_clips

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

With no annotations, the description carries full behavioral disclosure. It reveals ordering ('newest first'), scope ('full retention window'), limitations ('no separate date-range filter'), and how data fields (date, msec) relate to get_snapshot. This goes well beyond a basic read-only hint.

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 two tight paragraphs: the first sentence states purpose clearly, and the second adds valuable context about retention and usage. Every sentence contributes new information without redundancy.

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 is robust for behavior and integration, covering retention, ordering, and linkage to get_snapshot. The output schema covers return values, so no need to explain those. However, the missing parameter semantics for limit and the implicit handling of camera make it slightly incomplete overall.

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 0%, so the description must compensate for parameter meanings. It only implicitly references the camera parameter via 'for a camera' and completely omits the limit parameter. This is a significant gap given the description is the sole source of semantics.

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 opens with a clear, specific verb and resource: 'List recorded video segments for a camera, newest first.' This distinguishes it from sibling tools like list_cameras and list_alerts by focusing on video segments and their ordering.

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 clear context on when to use this tool: it covers the full retention window and lacks a date-range filter, implying it's for retrieving all available segments. It also mentions integration with get_snapshot, but does not explicitly exclude alternative tools or state when-not-to-use.

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