cleanup_generation_job

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

With no annotations, the description carries the full behavioral burden and usefully discloses both removal of job data and default preservation of final deliverables. It does not explain whether removal is irreversible, exactly what data is deleted, or how running jobs are affected.

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 single compact sentence front-loads the destructive action and immediately states the important preservation default. Both clauses add invocation-relevant information without filler.

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 basic action and default are clear, but the absence of annotations and an output schema leaves important gaps for a destructive operation. Deletion scope, permanence, job-state prerequisites, and the expected outcome are not described.

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. Preserving final deliverables gives practical meaning to keep_final beyond its boolean type and title, while job_id is only implicitly identified as the target job with no format or source guidance.

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 and resource: "remove job data," and clarifies that final deliverables are preserved by default. It does not explicitly distinguish this cleanup operation from lifecycle siblings such as cancel_generation.

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?

Deliberate cleanup while retaining final outputs is an implied use case. However, there is no guidance about eligible job states, when cleanup should occur, or when to use cancel_generation or artifact-retrieval tools instead.

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