Gemini Delete Cache Tool

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

No annotations are provided, so the description carries the full burden. 'Delete' implies a destructive, likely irreversible mutation, but the description never states permanence, whether deletion of a nonexistent cache errors, or any permission requirements. For a destructive cache operation with zero annotation coverage, this is a significant disclosure gap.

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 economical sentence with the verb front-loaded and no wasted words. It is terse to the point of under-specification, but it is structurally clean.

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 input schema is fully documented and an output schema exists, so return values need no explanation. However, for a destructive operation with no annotations at all, the description should at minimum note irreversibility or error behavior; as written it is only minimally complete.

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?

There is a single parameter (cache_name) with 100% schema description coverage, so the schema already documents it fully. The description adds no format or naming-convention detail beyond the schema, which is the expected baseline when schema coverage is complete.

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 (delete) and resource (content cache), which is unambiguous on its own. It does not, however, distinguish this tool from sibling cache operations (gemini_create_cache_tool, gemini_query_cache_tool, gemini_list_caches_tool), leaving sibling differentiation to the name alone.

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?

There is no guidance on when to use this tool versus the other cache tools, no prerequisites (e.g., whether the cache must exist or be unused), and no mention of alternatives. The agent must infer everything from context.

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