Reverse Search Frame

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false, idempotentHint=false): it discloses that execution publicly uploads the PNG to Uguu, verifies hosted bytes, submits the URL to Lens, requires both explicit grants and an enabled Serper credential, and warns that similarity suggestions never assert entity identity. It even flags that publication retention/deletion and live service schemas are unqualified.

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?

Four dense sentences, front-loaded with the purpose before mechanics and caveats, and each sentence carries distinct operational weight. The closing sentence on retention and live-service schemas is slightly jargon-heavy but still earns its place as an uncertainty disclosure.

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, and the annotations cover the safety profile. Given the nested capture payload and openWorldHint, the description supplies exactly the missing pieces: the public-upload side effect, the dual-grant requirement, and the identity-claim caveat.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning to the gatekeeping parameters by explaining that submission requires 'both explicit grants' (authorize_public_upload and authorize_submission) and an enabled credential, and that the default path is a plan rather than an upload.

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+resource ('reverse-search one captured frame') and names the underlying mechanism ('using Serper Lens'), which nothing else in the sibling list does. An agent can distinguish it from image_segment, vision_grounding, or video_frame without opening any 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?

'Plan or reverse-search' plus the required grants and credential implies the dry-run vs. execute split and a precondition, but the description never names when to prefer this over sibling visual tools or what to do instead. Usage is implied rather than routed.

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