Epic: Improved Tool Usage and Definitions

[mattKorwel]

Overview

This epic focuses on overhauling current tool usages and definitions to optimize for Gemini 3.0. As identified in the "Planning: Make Gcli smarter" session, many existing tool definitions are heavily based on the constraints of older models (2.5), leading to counterproductive "handholding" that restricts the newer model's proficiency with complex, terminal-centric operations like Bash piping.

Key Objectives

• Gemini 3.0 Alignment: Remove redundant technical restrictions in tool definitions that hinder the model's natural ability to manage its own context.
• Improved Tool Descriptions: Rewrite tool descriptions and parameter schemas based on feedback from the "One Recipe" (O team) and "Jet Ski" benchmarks.
• Simultaneous Prompting Updates: Coordinate tool changes with system prompt overhauls, as the two are deeply interdependent for optimal performance.
• Generic & Cross-Platform Focus: Ensure tools (like grep/glob) are defined generically enough to work across platforms while remaining high-signal for the model.

Core Strategy

• Terminal-Centric Approach: Leverage the newer model's Bash proficiency, allowing it to perform more exploratory actions (e.g., using piping or redirection to limit output) rather than relying on strictly gated tool parameters.
• Context Frugality: Design tools to be "frugal" with the context budget, favoring targeted results over large dumps.
• Unified Front: Align tool names and behaviors with other internal agent teams (DeepMind, Jewels, anti-gravity) to benefit from shared model training efforts.

---

Based on the planning session: Planning: Make Gcli smarter