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

Beyond the annotations (which already declare readOnly/idempotent/openWorld/non-destructive), it discloses that the call is stateless, capped at 32 KB, rate-limited to 60 RPM, has a 150 s timeout, and supports demo/L402 payment modes. It also states the failure behavior (HTTP 400 on invalid input), which is exactly the kind of operational context the description should carry.

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?

Three sentences, front-loaded with purpose then routing then operational constraints; almost every clause carries information. It is dense to the point of being slightly packed (payment, size, rate, timeout, error code in one sentence), but nothing is clearly wasteful.

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?

An output schema exists so return values need not be described; the description covers the missing pieces an agent needs — auth/payment path, size and rate limits, timeout, and error behavior. Nothing required to invoke it correctly is absent.

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 both parameters are already documented. The description only restates the 'input' role and the execution_mode default, adding no new syntax or format guidance beyond the schema — the baseline of 3 for schema-complete tools 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 verb ('Dispatches') and resource ('Google's Antigravity autonomous agent') with the scope of what the agent does (multi-step planning, tool orchestration, verified execution). It explicitly names the sibling it is not (conduct_deep_research_investigation), so an agent can route without opening either schema.

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?

Gives a positive trigger ('multi-stage software engineering or workflow tasks that require autonomous planning') and a negative rule with the alternative tool named for research dossiers. The routing decision is fully specified rather than inferred.

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