list_checkpoints

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

The readOnlyHint annotation is consistent with the non-mutating 'List' verb, so there is no contradiction. The description adds modest context about the source ('mounted Drive') and completeness of the manifests, but it does not mention pagination, size limits, or what the returned manifests contain.

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, direct sentence with no filler. The action and object are front-loaded, and every word earns its place.

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 one-parameter, read-only tool, the description is minimally adequate, but it leaves gaps: project semantics are undocumented, and there is no output schema to clarify the return format. The agent can invoke the tool but cannot fully predict how results will be shaped or filtered.

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?

The schema has 0% description coverage, and the description does not mention the 'project' parameter or how it affects the listing. An agent cannot tell whether project filters results, changes paths, or requires a specific value, so the description fails to compensate for the schema gap.

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') with a specific resource ('complete checkpoint manifests') and location ('mounted Drive'), making the tool's purpose unambiguous. It is clearly distinct from sibling tools like restore_workspace or save_workspaces.

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?

No guidance is provided about when to use this tool versus alternatives such as restore_workspace or save_workspaces. The description implies its use for listing manifests but does not state prerequisites, exclusions, or why an agent would choose it over a sibling.

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