reverse_image_search

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 merely restates that it finds visually matching images, without disclosing any behavioral traits such as read-only status, expected result format, rate limits, or authentication needs.

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 concise and front-loaded with the main purpose. The 'Operations' section is somewhat redundant with the input schema but provides necessary context for the args object. Slight repetition prevents a 5.

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?

Given the absence of an output schema and the presence of sibling tools with overlapping functionality, the description is incomplete. It does not describe what the result looks like, what kind of images are returned, or any limitations. A simple reverse image search tool needs more detail.

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 covers the operation and args wrapper, but the actual 'url' parameter is only mentioned in the description as 'required: url'. This adds necessary but minimal meaning; the description does not explain what forms of URL are acceptable or how the URL is used.

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 that the tool performs reverse image search using an image URL, with a specific verb and resource. However, it does not distinguish itself from sibling tools like realtime_image_search or realtime_lens_data, so it misses the full bar for a 5.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. It only outlines the internal operation structure, which is not usage guidance.

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