web_lookup

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

No annotations are provided, so the description carries full burden. It mentions delegation to Antigravity CLI but lacks disclosure of behavioral traits such as side effects, permissions, latency, failure behavior, or rate limits. Given the external web access, more transparency is expected.

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 two sentences, front-loaded with the tool's purpose and examples. It is efficient, though the first sentence is dense and could be slightly 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?

The description explains the tool's purpose and provides usage guidance, but lacks information about return values (no output schema) and error handling. Given the absence of annotations, it is adequate but not fully complete.

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?

The input schema covers 100% of parameters with descriptions. The description adds no additional meaning beyond the schema (e.g., it does not elaborate on query format or cwd usage). Baseline score of 3 is appropriate given full schema coverage.

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 delegates web/documentation lookups to an external CLI for library docs, API references, etc. It specifies the verb 'delegate' and the resource 'web/documentation lookup', and provides a usage hint. However, it does not explicitly differentiate from sibling tools like deep_search or delegate.

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 description explicitly says 'USE THIS when you need information you don't have or that may be newer than your training data,' providing clear context for when to use the tool. It does not mention when not to use it or list alternatives, but the guidance is sufficient for most cases.

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