veo_cleanup_sessions

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

With no annotations, the description must carry the full burden. It discloses that it removes state files and optionally downloaded videos, which is useful, but it does not warn about irreversibility or mention filtering behaviors like 'completed_only' or the age threshold. This is moderate transparency but lacks depth for a destructive operation.

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 two sentences, front-loaded with the main purpose, and every word earns its place. It is concise, clear, and well-structured.

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 description covers the core behavior and the output schema handles return values. It does not mention irreversibility or the exact filtering criteria, but for a simple cleanup tool with fully documented parameters, it is adequately complete. A warning about permanence would elevate it further.

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 documents both parameters fully (100% coverage), so the baseline is 3. The description adds some context by mentioning 'state files' and 'downloaded videos', but it does not explain the parameters directly or add meaning beyond what the schema already provides.

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 clearly states the verb 'clean up' and the resource 'generation sessions and their files', distinguishing it from sibling tools like 'veo_list_sessions' and 'veo_download_video'. It is specific and unambiguous.

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 provides clear context for when to use this tool (old sessions cleanup) and implicitly contrasts it with list/download tools. However, it does not explicitly mention when not to use it or name alternative tools, so it stops short of a 5.

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