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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Reverse-image-search links', without stating whether it uploads an image, takes a URL, has rate limits, or produces side effects. The behavior is underspecified for a tool with no safety hints.

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, which is concise, but it omits essential information. It is under-specified rather than efficiently minimal, leaving the parameter and behavior unexplained.

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 single parameter and no annotations, the description is incomplete. It does not explain what the parameter does or what the output contains, even though an output schema exists. For a simple tool, the lack of parameter guidance is a critical gap.

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 has one parameter 'q' with no description, and schema description coverage is 0%. The tool description provides zero clarification about what 'q' represents (e.g., an image URL, a query string, or an identifier). The agent cannot determine how to fill the parameter correctly.

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 clear verb-resource pair: 'Reverse Image' for 'reverse-image-search links', and it names the specific engines (Lens/Yandex/TinEye/Bing), which distinguishes it from siblings like imagerev or imagephash. It's not a tautology and conveys the core function well, though it lacks detail on how the links are produced.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent to infer when reverse-image-search links are appropriate.

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