List Sequence Checkpoints

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds context about the artifact origin (created by create_sequence_checkpoint) and the optional clone-source filter, but does not describe pagination, limits, 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?

The description is a single efficient sentence that front-loads the main action and includes the key optional filter. The trailing 'Read-only' is redundant with the annotations, but it is minor and does not bloat the description.

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 simple read-only list tool with one optional parameter, an output schema, and complete annotations, the description is nearly sufficient. It could more explicitly connect the optional sequence_id parameter to 'list all checkpoints when omitted,' but the schema already marks the parameter as optional and the output schema covers return fields.

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 sequence_id as 'Only list checkpoints of this sequence (ID or name).' The description adds the notion of 'cloned from one sequence,' which loosely maps to the same parameter but provides no additional format, default, or behavior details beyond the schema.

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 uses a specific verb ('List') and resource ('[checkpoint] sequences'), ties the resource to its creator tool (create_sequence_checkpoint), and mentions the key optional filter. This distinguishes it from sibling tools like list_sequences or list_sequence_tracks.

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 implies usage by noting these are sequences created by create_sequence_checkpoint and that filtering by a source sequence is optional. It does not explicitly state when to prefer this over list_sequences or list_sequence_tracks, nor does it give exclusions or alternatives.

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