List Sequence Checkpoints

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the trailing 'Read-only' is a restatement rather than new information. The genuinely additive content is the enumeration of returned fields, but an output schema exists and the description doesn't go beyond it (no pagination, ordering, or empty-result behavior).

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 with no filler; the optional filter clause is placed after the core purpose. Slightly dense, and the bracketed '[checkpoint]' token is an odd artifact, but nothing is wasted.

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?

For a single-optional-parameter read tool with an output schema and full annotation coverage, the description supplies enough to call it correctly and understand the result shape. Only minor gaps remain (ordering, pagination, behavior with no checkpoints), which the output schema likely resolves.

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% and the single parameter is fully documented there, so the baseline is 3. The phrase 'cloned from one sequence' adds a small nuance to sequence_id's semantics (matching on source lineage, not just existence), but the description does not clarify ID-vs-name handling or default behavior.

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 (List) and resource (sequence checkpoints), names the creating sibling (create_sequence_checkpoint) so the agent can place it in the right workflow, and enumerates what each entry contains (labels, timestamps, track and clip counts). It is clearly distinguishable from the many other list_* tools.

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?

Provides clear context for when this applies: after checkpoints have been made by create_sequence_checkpoint, and optionally narrowed to checkpoints cloned from a single source sequence. It does not state exclusions or name a competing listing tool, but none exists among the siblings, so inference is low-risk.

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