cli_execute

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

No annotations are provided, so the description carries the full burden. It does disclose two meaningful traits: execution must be non-interactive, and mutation is gated behind allow_mutating=true (default false). But it says nothing about what happens on failure, how output is returned, or the destructive potential of arbitrary command execution.

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?

Two tight sentences with the core capability front-loaded and the mutation precondition following immediately. Nothing is wasted, though given the complexity of an arbitrary-CLI tool the brevity borders on under-specification.

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?

For a tool that executes arbitrary CLI commands with 5 parameters, no annotations, and no output schema, the description is too thin. It omits what 'args' should contain, what 'management commands' means, expected output/error shape, and the purpose of account and timeout_sec.

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 only 20% — only 'workspace' is documented in the schema. The description adds meaning only for allow_mutating, leaving args, account, and timeout_sec undocumented in both the schema and the description. It fails to compensate for the coverage gap.

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 verb and resource: 'Execute any non-interactive Antigravity CLI argv.' The phrase 'for full CLI coverage' signals this is the generic escape hatch, which loosely implies a relationship to the named siblings (submit_job, health_check, etc.), but the description never explicitly contrasts itself with them.

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?

It gives one concrete precondition ('Mutating management commands require allow_mutating=true'), which is useful. However, it offers no guidance on when to prefer this generic executor over the many specific sibling tools like submit_job or get_job_status, leaving that routing decision to inference.

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