run_antigravity_coding_task

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

Discloses behavioral traits like strict contracts, Git verification, and diagnostics, but given no annotations, more detail on error handling or permissions would improve clarity.

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?

Single sentence with bullet-like features is concise, but could be structured with separate sections for purpose and behavior to improve scannability.

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?

Lacks detail on return values, error scenarios, and parameter dependencies; for a tool with 12 parameters and no output schema, the description is incomplete.

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?

Description does not explain individual parameters; with low schema coverage (33%), it fails to compensate, leaving many parameters like timeoutSeconds and mode undocumented.

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 the tool invokes the Antigravity CLI for coding, with specific features like execute/plan contracts and Git verification, distinguishing it from siblings like plan_with_codex.

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?

No guidance on when to use this tool versus alternatives; lacks context for when to choose this over run_gemini_coding_task or other siblings.

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