ping

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

With no annotations, the description must carry the full burden. It reveals that the tool verifies responsiveness, but it does not disclose that an optional prompt is sent, what the success/failure response looks like, or whether there are any side effects. 'Verifies' hints at read-only behavior, but too much is left to inference.

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 one short sentence, front-loads 'Health check,' and avoids repeating the tool name (ping) as a verbatim label. It could not be more concise.

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 simple, optional-parameter ping, the description plus schema covers the basic call: run with no arguments and get verification. However, it is incomplete because the prompt parameter is unexplained and no usage context is given; this is adequate but has clear gaps.

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 0%, and the description does not mention the prompt parameter at all. The schema gives only a title and default, so an agent cannot tell why prompt exists or how it affects the health check.

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 states a specific action and resource: 'verifies that the Antigravity CLI or backend responds,' clearly identifying a health-check tool. This is distinct from the sibling tools (ask, review, generate, list, check-quota) even without naming 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?

No guidance is given about when to run this check versus using a sibling tool such as ask-antigravity or check-quota. The phrase 'Health check' implies pre-flight connectivity verification, but the description never states this or any exclusions.

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