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

Annotations already establish that this is a safe, idempotent read. The description adds useful behavioral context—newest-first ordering and the required scope—but does not explain pagination behavior or what information each checkpoint contains.

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 short sentences, front-loaded with the operation and followed by the ordering and auth requirement. No filler or 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?

For a simple two-parameter list tool with rich safety annotations, the description gives enough to call it correctly: it identifies the workspace scope, ordering, and required permission. The main omission is parameter-level detail, especially around limit.

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 should compensate, but it only implies the workspace_id via 'a workspace's checkpoints' and says nothing about the limit parameter, its default of 50, or its 1–200 range.

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 states a specific verb and resource ('List a workspace's checkpoints') and adds ordering ('newest first'), making the operation clear and distinguishable from get_checkpoint and create_checkpoint. It stops short of explicitly naming how it differs from adjacent checkpoint 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?

The listing purpose implies when to use it, and the required 'context:export' scope is stated, but there is no explicit guidance on when to choose this over get_checkpoint or how to handle multiple checkpoints versus a single checkpoint.

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