gemini

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

With no annotations provided, the description must disclose behavioral traits, but it only lists capabilities without addressing side effects, safety, or operational nuances. The schema hints at behaviors like yolo mode (auto-approve), sandbox, and interactive mode, but the description itself does not mention these or any potential risks, making it inadequate for a command-execution tool.

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 exceptionally concise, consisting of two short sentences that immediately state the core action and enumerate supported modes. There is no redundancy or fluff, and the most critical information is front-loaded.

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?

Despite having six parameters and no output schema, the description provides only a high-level summary of capabilities. It does not explain how the modes interrelate, what the tool returns, or any execution details, leaving the agent to rely entirely on the schema for context. This is insufficient for a tool of this complexity.

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 100%, so each parameter is already well-defined in the input schema. The tool description adds no additional meaning beyond the schema, which is acceptable per the baseline; it neither enhances nor detracts from parameter understanding.

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 'Execute Gemini CLI commands' with a specific verb and resource, and further enumerates the tool's main capabilities: queries, interactive mode, and extension management. This fully clarifies the tool's purpose and differentiates it from potential siblings (though none are present).

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 on the tool's intended use cases by listing the three supported modes (queries, interactive mode, extension management). While it does not explicitly state when not to use this tool or name alternatives, the absence of siblings and the explicit enumeration offer sufficient guidance for an agent to determine applicability.

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