gemini_cli_execute

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

No annotations are provided, so the description must carry the full burden. It discloses that execution is synchronous and supports interactive/non-interactive prompts, but omits side effects, return values, timeout behavior, and safety implications of running CLI commands. For a command-execution tool, this is a significant 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?

The description is a single concise sentence with no meaningful bloat, and the key synchronous behavior is front-loaded. It loses a point for the slightly generic 'with configurable parameters' phrase, which adds little information, but overall it is efficiently written.

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 15 optional parameters, no annotations, and no output schema, a one-sentence description is insufficient. It omits return value semantics, output format behavior, timeout handling, and any warnings about potential system effects, leaving an agent without enough context to invoke the tool confidently.

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%, with all 15 parameters documented in the input schema. The description only says 'configurable parameters' and adds no parameter-specific meaning beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific action ('Execute Gemini CLI synchronously') and clearly distinguishes itself from the async sibling by emphasizing synchronous mode. Also notes support for both interactive and non-interactive prompts, giving a clear functional identity.

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 word 'synchronously' implies use when blocking execution is desired, and the sibling names hint at an async alternative. However, there is no explicit guidance on when to choose this tool over gemini_cli_execute_async or how gemini_cli_check_result fits in, leaving the selection largely to inference.

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