realtime_lens_data

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 clarifies each operation's behavior (e.g., OCR extracts text, exact matches) but does not disclose potential error conditions, response format, or any side effects. The read-only nature is implied but not explicitly stated.

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 well-structured with a clear intro, a bulleted list of operations with required parameters, and a concise 'When to use' section. Every sentence serves a purpose, with no redundant information.

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 with five sub-operations, the description covers operation semantics, required input structure, and usage context. It does not describe the output schema, but the absence of an output schema makes the one-line descriptions of returns (e.g., 'Image to Text (OCR)') reasonably sufficient. It is nearly complete for an AI agent to select and invoke correctly.

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 schema provides 100% coverage of the top-level parameters (operation and args), but the args object is generic. The description compensates by stating that each operation requires 'url' inside args and giving one-line descriptions for each operation, adding meaning beyond the schema's enum values.

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 'Google Lens on an image URL' and enumerates specific sub-operations: visual matches, exact matches, object detection, and OCR. It distinguishes this tool from the sibling reverse_image_search by focusing on deep visual analysis rather than simple reverse lookup.

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 includes an explicit 'When to use' section: use for deep visual analysis of an image, and for simple reverse lookup use reverse_image_search. This directly names an alternative tool and clarifies the boundaries of use.

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