job_checkpoints

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the tool lists completed checkpoints and includes retained/deleted availability, which is useful behavioral context. However, it does not explain whether the operation is read-only, whether it requires specific permissions, or what the output structure looks like beyond the existence of an output schema.

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, concise sentence that front-loads the primary action ('List completed managed checkpoints') and adds a useful qualifier. It is appropriately sized for a simple list operation with one parameter.

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 tool has a simple input schema (one required parameter) and an output schema, so the description does not need to explain return values. However, with no annotations and no usage guidance, the description leaves some gaps: it does not clarify whether 'managed checkpoints' are job-specific, how to interpret retained/deleted availability, or how this relates to sibling tools like configure_checkpoints.

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 the undocumented job_id parameter. The description does not explain what job_id refers to or how to obtain it, but the parameter name is self-explanatory in context. The description adds no semantic detail beyond the schema, so a baseline score of 3 is appropriate.

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 ('List') and resource ('completed managed checkpoints'), and adds a scope qualifier ('retained/deleted availability') that distinguishes it from generic checkpoint tools. It does not explicitly name a sibling alternative, but the verb+resource combination is clear enough to identify the operation.

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 context: it lists completed managed checkpoints and includes availability status, so an agent can infer it is for inspecting checkpoint history. However, it does not explicitly state when to use this tool versus alternatives like configure_checkpoints or job_status, nor does it mention any prerequisites or exclusions.

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