gemini_delete_file

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

Annotations already set destructiveHint: true, so the description does not need to restate destructiveness. It adds valuable context: the file's ~48h expiry, the side effect that referencing calls will fail with a generic 404, and the instruction to only delete when finished. This goes beyond the annotations.

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 long, front-loading the core action and key constraints. Every sentence adds value: the first states the purpose and expiry, the second explains the consequence and correct usage. No unnecessary words.

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?

Given the tool's simplicity (a deletion operation), the annotation coverage (destructiveHint, readOnlyHint false), schema richness (2 params with 100% coverage), and lack of output schema, the description provides sufficient context. It covers purpose, behavior, parameter semantics, and usage guidance. Minor gaps: no mention of whether deletion is permanent or if there's any recovery.

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 coverage is 100%, so baseline is 3. The description adds meanings: it explains that 'confirm' must be true to proceed, otherwise returns a preview, and clarifies that 'file_uri' can be the 'files/<id>' reference or full URI. This enhances understanding beyond the schema descriptions.

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 the specific verb 'Delete' and identifies the resource as 'an uploaded file from the Gemini Files API'. It clearly differentiates the tool from siblings by specifying its unique action (deletion) and mentions the ~48h expiry, which is specific to this tool.

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 implicitly advises when to use the tool ('delete only references you are finished with') and warns about consequences of misuse (404 errors for other tool calls). It does not explicitly state when not to use or list alternatives, but the context is clear enough for an AI agent.

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